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 Wed, 11 Nov 2015 02:05:11 GMT

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

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_r44494260
  
    --- Diff: core/src/main/java/org/apache/accumulo/core/client/impl/ScannerOptions.java
---
    @@ -244,4 +247,20 @@ public void setBatchTimeout(long timeout, TimeUnit timeUnit) {
       public long getBatchTimeout(TimeUnit timeUnit) {
         return timeUnit.convert(batchTimeOut, TimeUnit.MILLISECONDS);
       }
    +
    +  @Override
    +  public void setContext(String context) {
    +    this.context = context;
    --- End diff --
    
    My thinking is there is no way to distinguish between a user accidentally passing null
when they did not mean to and a user trying to clear the context.  However if we do not accept
null (users must call clearContext insead), then we can always detect the case where a user
accidentally passes null and fail fast.   


> 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