[jira] [Commented] (ACCUMULO-4609) Import scope for table configs, especially for iterators to validate k/v

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939460#comment-15939460 ] 

Christopher Tubbs commented on ACCUMULO-4609:
---------------------------------------------

Individual k/v pairs are not inspected during a bulk import. Data is not iterated over during this operation.

If I understand your request correctly, it seems you're looking for the ability to perform some key/value filtering/transformation during first scan or major compaction after a file is bulk imported. is that correct? I think this is probably already possible with the existing scan/majc scopes. Are these insufficient?


> 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 and 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)