[
https://issues.apache.org/jira/browse/ACCUMULO-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190590#comment-13190590
]
David Medinets commented on ACCUMULO-343:
-----------------------------------------
In for a penny ... I've run through all of the examples and the user manual but
I managed to misunderstand what was happening with the setauths command and
visibility labels.
Can examples using no visibility labels (i.e., no -l option on the insert) be
added to README.visibility for completeness? If there are no visibility labels
is that equivalent to "public" so that anyone can see it?
Please add something like "Accumulo does not keep sort of list of visibilities.
Furthermore there is no definition of visibilities, so there is no such thing
as defined and undefined visibilities. This might lead to an issue with
misspelled visibility labels. Keep this in mind when debugging a misbehaving
application." somewhere in the README.visibility file.
Can you add a few scan examples to the "Inserting data with visibilities"
section? For example,
{noformat}
# Clear authorizations
test> setauths -c
test> scan
# no records are displayed because no authorizations are set and all records in
the test table have visibility labels.
test> scan -s broccoli
21 21:56:40,121 [shell.Shell] ERROR: java.lang.RuntimeException:
org.apache.accumulo.core.client.AccumuloSecurityException: Error
BAD_AUTHORIZATIONS - The user does not have the specified authorizations
assigned
test> setauths -s apple
test> scan
# no records are displayed because the one record in the table needs both
"apple" and "carrot" authorizations due to the visibility label.
test> setauths -s apple,carrot
test> scan
florida george:age [(apple&carrot)|broccoli|spinach] 50
test> setauths -s broccoli
test> scan
florida george:age [(apple&carrot)|broccoli|spinach] 50
test> setauths -s apple,carrot,broccoli
# If you have several authorizations, you can use the scan command to display
only specific authorizations.
test> scan -s broccoli
florida george:age [(apple&carrot)|broccoli|spinach] 50
# Of course, the visibility logic is still applied, therefore you must specify
both apple and carrot
test> scan -s apple,carrot
florida george:age [(apple&carrot)|broccoli|spinach] 50
{noformat}
Is there any way to set the VisibilityConstraint as a default constraint for
all tables?
> 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
