[
https://issues.apache.org/jira/browse/ACCUMULO-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646018#comment-14646018
]
Dave Marion commented on ACCUMULO-3948:
---------------------------------------
Another use of this feature would be to support rolling upgrades of a client
application. Having two versions of an application running against the same
table at the same time, using different versions of scan iterators. MinC and
MajC iterators would still use the context name applied to the table via the
table configuration.
> 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
>
> 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)
