accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-360) Bulk importing Keys with invalid ColumnVisibility doesn't fail until scan
Date Thu, 27 Dec 2012 21:08:12 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Turner resolved ACCUMULO-360.
-----------------------------------

    Resolution: Fixed
    
> 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: Keith Turner
>              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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message