accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3948) Enable A/B testing of scan iterators on a table
Date Mon, 16 Nov 2015 20:49:11 GMT


ASF GitHub Bot commented on ACCUMULO-3948:

Github user keith-turner commented on a diff in the pull request:
    --- Diff: core/src/main/java/org/apache/accumulo/core/client/ ---
    @@ -242,4 +242,31 @@
        * @since 1.8.0
       long getBatchTimeout(TimeUnit timeUnit);
    +  /**
    +   * Sets the name of the classloader context on this scanner. See the administration
chapter of the user manual for details on how to configure and use
    +   * classloader contexts.
    +   *
    +   * @param classLoaderContext
    +   *          name of the classloader context
    +   * @throws NullPointerException
    +   *           if context is null
    +   * @since 1.8.0
    +   */
    +  void setClassLoaderContext(String classLoaderContext);
    --- End diff --
    There are at least two ways to do this check.   Do it when setClassLoader is called. 
Or do it when the thrift calls startScan and continueScan are made.  An exception could be
added to these thrift calls.  How were you thinking of doing the check?
    For getting server side table props you can look into the implementation of `TableOperations.getProperties()`

> Enable A/B testing of scan iterators on a table
> -----------------------------------------------
>                 Key: ACCUMULO-3948
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message