You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/10/20 19:50:27 UTC

[jira] [Commented] (ACCUMULO-3948) Enable A/B testing of scan iterators on a table

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

Josh Elser commented on ACCUMULO-3948:
--------------------------------------

bq. We can support users passing in a context name to use for the scan on existing tables. 

Sounds like a good time to consider making a {{ScannerConfig}} (and {{BatchScannerConfig}}) to match the {{BatchWriterConfig}}. Would be neat.

> Enable A/B testing of scan iterators on a table
> -----------------------------------------------
>
>                 Key: ACCUMULO-3948
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3948
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Dave Marion
>            Assignee: Dave Marion
>             Fix For: 1.8.0
>
>
> Classpath contexts are assigned to a table via the table configuration. You can test at scale by cloning your table and assigning a new classpath context to the cloned table. However, you would also need to change your application to use the new table names and since we cannot disable compactions you would start to consume more space in the filesystem for that table. We can support users passing in a context name to use for the scan on existing tables. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)