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 Thu, 12 Nov 2015 17:05:10 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,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?
    Thats a good point.  We could be vauge about it and just say see the user manual for more
information.   Also since its not a URL, we can not run tools to check for bad links.
    > 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.
    I think its reasonable to assume that someone will start using 1.8 w/o ever reading the
user manual and notice this new method in an IDE.  When they see the new method in the IDE,
currently it would not have much javadocs.  However there are nice docs elsewhere. It would
be nice to make the user aware of those docs and help them find them.  Personally I think
helping guide the user in this case is better than doing nothing because of the valid concern
that info pointed to may move.

> 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