You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Billie Rinaldi (Created) (JIRA)" <ji...@apache.org> on 2012/02/01 16:48:58 UTC
[jira] [Created] (ACCUMULO-360) Bulk importing Keys with invalid
ColumnVisibility doesn't fail until scan
Bulk importing Keys with invalid ColumnVisibility doesn't fail until scan
-------------------------------------------------------------------------
Key: ACCUMULO-360
URL: https://issues.apache.org/jira/browse/ACCUMULO-360
Project: Accumulo
Issue Type: Bug
Components: client
Affects Versions: 1.3.5
Reporter: Billie Rinaldi
Assignee: Billie Rinaldi
Fix For: 1.4.0
A Key is allowed to have an invalid ColumnVisibility so it can be used in a Range (see ACCUMULO-193). Also, we don't want Key to create a ColumnVisibility object to test the validity of a supplied Text, CharSequence, or byte[] visibility due to the large amount of overhead in doing so. This isn't a problem when writing Mutations to Accumulo, but during bulk import Keys are written directly to files. Thus the user doesn't receive an error for the invalid ColumnVisibility until scanning the table.
--
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
[jira] [Updated] (ACCUMULO-360) Bulk importing Keys with invalid
ColumnVisibility doesn't fail until scan
Posted by "Keith Turner (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Turner updated ACCUMULO-360:
----------------------------------
Fix Version/s: (was: 1.4.0)
1.5.0
Could modify the AccumuloFileOutputFormat to do this sanity check. To make it efficient could use a LRUHashMap of recently seen visibilities that were previously verified. Could also a sanity check of the time stamp to make sure its not MAX_LONG.
> Bulk importing Keys with invalid ColumnVisibility doesn't fail until scan
> -------------------------------------------------------------------------
>
> Key: ACCUMULO-360
> URL: https://issues.apache.org/jira/browse/ACCUMULO-360
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.3.5
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Labels: bulk, visibility
> Fix For: 1.5.0
>
>
> A Key is allowed to have an invalid ColumnVisibility so it can be used in a Range (see ACCUMULO-193). Also, we don't want Key to create a ColumnVisibility object to test the validity of a supplied Text, CharSequence, or byte[] visibility due to the large amount of overhead in doing so. This isn't a problem when writing Mutations to Accumulo, but during bulk import Keys are written directly to files. Thus the user doesn't receive an error for the invalid ColumnVisibility until scanning the table.
--
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