[jira] [Issue Comment Edited] (ACCUMULO-343) Using non-existant visibility with command-line insert should display error message.

["John Vines (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190593#comment-13190593 ] 

John Vines edited comment on ACCUMULO-343 at 1/22/12 3:29 AM:
--------------------------------------------------------------

I'm definately all for clarifying the READMEs, it's nice to get a fresh pair of eyes on them and finding the issues.

We do not currently have a mechanism in place for default constraints, nor do we plan to. However, you should be able to set a system-wide constraint, either via the site.xml file or via the same command in the example, but sans -t <tablename>. However, I put emphasis as should as we recently stumbled across some issues with constraints (I believe tickets 320-325). Most of them deal with operating at the various site/system/table levels of configuration so you may not be seeing this behavior in 1.4. I believe the biggest problem you will have with this in 1.4 and below is that the only way to disable a higher level constraint (e.g. disable a site constraint for a single table) is by putting in a new constraint for that numeration. This is because constraints are (currently) numerated and replacing that constraint # with a blank one will result in an error.
tldr; Yes, you can set them at the system level or in the site.xml file which will have it belong to all tables, but you will probably have issues disabling the constraint for a specific table.

I hope I was clear in explaining that, it is a bit late on my part. Let me know if you need any clarification.
                
      was (Author: jvines):
    I'm definately all for clarifying the READMEs, it's nice to get a fresh pair of eyes on them and finding the issues.

We do not currently have a mechanism in place for default constraints, nor do we plan to. However, you should be able to set a system-wide constraint, either via the site.xml file or via the same command in the example, but sans -t <tablename>. However, I put emphasis as should as we recently stumbled across some issues with constraints (I believe 320-325). Most of them deal with operating at the various site/system/table levels of configuration so you may not be seeing this behavior in 1.4. I believe the biggest problem you will have with this in 1.4 and below is that the only way to disable a higher level constraint (e.g. disable a site constraint for a single table) is by putting in a new constraint for that numeration. This is because constraints are (currently) numerated and replacing that constraint # with a blank one will result in an error.
tldr; Yes, you can set them at the system level or in the site.xml file which will have it belong to all tables, but you will probably have issues disabling the constraint for a specific table.

I hope I was clear in explaining that, it is a bit late on my part. Let me know if you need any clarification.
                  
> Using non-existant visibility with command-line insert should display error message.
> ------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-343
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-343
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: David Medinets
>            Priority: Minor
>
> When I inserted a record with a visibility label that was undefined, nothing happens. These are the steps I followed:
> {noformat}
> $ start the command line client.
> > createtable test                            
> test> insert florida george age 50 -l readable    
> test> scan
> {noformat}
> Notice that there are no error messages or inserted records. Now let's define the visibility label and try again.
> {noformat}
> test> setauths -u root -s readable
> test> insert florida george age 50 -l readable    
> test> scan
> florida george:age [readable]    50
> {noformat}
> Once the visibility is defined, the record is properly inserted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira