[ACCUMULO-360] Bulk importing Keys with invalid ColumnVisibility doesn't fail until scan

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.5-incubating
• Fix Version/s: 1.5.0
• Component/s: client
• Labels: bulk visibility
• Assignee: Keith Turner
• Reporter: Billie Rinaldi
• Created: 01/Feb/12 15:47
• Updated: 20/Feb/14 23:29
• Resolved: 27/Dec/12 21:06

Description

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.

Issue Links

• is duplicated by: ACCUMULO-651 Key constructor, Column Visibility can corrupt a table
• is related to: ACCUMULO-461 Provide convenient mechanism for checking constraints client side