accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Blum (JIRA)" <>
Subject [jira] [Created] (ACCUMULO-4435) WholeColumnFamilyIterator doesn't work after re-init
Date Wed, 31 Aug 2016 17:08:21 GMT
Daniel Blum created ACCUMULO-4435:

             Summary: WholeColumnFamilyIterator doesn't work after re-init
                 Key: ACCUMULO-4435
             Project: Accumulo
          Issue Type: Bug
          Components: core
    Affects Versions: 1.6.5
            Reporter: Daniel Blum
            Priority: Minor

When using WholeColumnFamilyIterator this exception is thrown:

java.lang.IllegalStateException: never been seeked
        at org.apache.accumulo.core.iterators.WrappingIterator.hasTop(
        at org.apache.accumulo.core.iterators.user.WholeColumnFamilyIterator.hasTop(
        at org.apache.accumulo.core.iterators.system.SourceSwitchingIterator.readNext(
        at org.apache.accumulo.tserver.Tablet.lookup(
        at org.apache.accumulo.tserver.Tablet.lookup(
        at org.apache.accumulo.tserver.TabletServer$ThriftClientHandler$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

I THINK this is caused by re-initialization of the iterator stack. When this happens
may end up returning without calling seek() on its source (because it gets a range with effectively
nothing in it). This would be fine except that WCFI.hasTop() calls hasTop() on its source;
since the source has not been seeked yet, the exception is thrown.

WholeRowIterator does not run into this problem in spite of using the same seek logic because
its hasTop (actually RowEncodingIterator.hasTop) does not check the source's hasTop. (The
way RowEncodingIterator and WCFI handle all of this does not really conform to the interface
definition - they should really keep track themselves of whether they have been seeked and
throw the appropriate exceptions.)

I actually encountered this in 1.6.2, but I can't select that as a version here. I believe
the problem also exists in 1.6.5 (and 1.7.2) based on inspecting the source, but cannot test
with those versions right now to confirm.

This message was sent by Atlassian JIRA

View raw message