accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3948) Enable A/B testing of scan iterators on a table
Date Thu, 12 Nov 2015 21:13:11 GMT

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

ASF GitHub Bot commented on ACCUMULO-3948:
------------------------------------------

Github user keith-turner commented on a diff in the pull request:

    https://github.com/apache/accumulo/pull/51#discussion_r44715330
  
    --- Diff: core/src/main/java/org/apache/accumulo/core/client/ScannerBase.java ---
    @@ -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 --
    
    What happens when a user sets a context that does not exists?  When this happens, does
the exception have an informative message that makes it easy for the user to determine what
happened?  Is there a test for this case? 


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

Mime
View raw message