[
https://issues.apache.org/jira/browse/ACCUMULO-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002391#comment-15002391
]
ASF GitHub Bot commented on ACCUMULO-3948:
------------------------------------------
Github user dlmarion commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/51#discussion_r44681496
--- Diff:
core/src/main/java/org/apache/accumulo/core/client/ScannerBase.java ---
@@ -242,4 +242,30 @@
* @since 1.8.0
*/
long getBatchTimeout(TimeUnit timeUnit);
+
+ /**
+ * Sets the name of the classloader context on this scanner
--- End diff --
And if the section number is added to the javadoc, who updates the javadoc
in the future versions of the code when the manual changes? I would think that
if you want to use the class loader context feature, then you have probably
already read the section in the manual to understand how to configure it.
> 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
>
> Attachments: ACCUMULO-3948.1-6-3.patch, TestIterator.patch
>
>
> 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)
