accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Downs (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-4609) Import scope for table configs, especially for iterators to validate k/v
Date Tue, 21 Mar 2017 14:35:41 GMT
Chip Downs created ACCUMULO-4609:
------------------------------------

             Summary: Import scope for table configs, especially for iterators to validate
k/v
                 Key: ACCUMULO-4609
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4609
             Project: Accumulo
          Issue Type: Wish
          Components: core
            Reporter: Chip Downs
            Priority: Minor


Recommend adding an "import" scope to the table configs, including the ability to set iterators
for k/v validation during bulk import.

Scenario: Administrator fails to change to the proper table when executing the importdirectory
command from the shell. Instead of an avalanche of scan and compaction failures due to unexpected
row, colf, colq, and visibility formatting, the import scope's iterator stack rejects the
offensive key/values maintains the integrity of the table.

Could happen? Definitely happens! Even a simple regex iter in such a scope could prevent a
lot of heartache.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message