accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3905) RowDeletingIterator does not work if columns are specified
Date Wed, 17 Jun 2015 19:51:00 GMT


Keith Turner commented on ACCUMULO-3905:

There is a [comment|]
on ACCUMULO-1801 that offers a workaround.

I think the deeper problem is that an iterator only has control over which column families
to fetch.  The RowDeletingITerator takes advantage of this, for example on [line 148|]
it adds the empty column family.  However with column qualifier filtering, thats done at a
lower level and iterators have no control over it.  See [ line 2005|].
 I thought there was an issue about the column qualifier filtering behavior, but I can not
find it.

> RowDeletingIterator does not work if columns are specified
> ----------------------------------------------------------
>                 Key: ACCUMULO-3905
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>            Reporter: Eric Newton
> (from the mailing list):
> {quote}
> It seem that there might be a bug in RowDeletingIterator:
> after using RowDeletingIterator I get expected results when querying by rowId and CF,
> scan \-b myrowid  \-c field/abc \-t table <---- doesn't return deleted rows as expected
> however if I add column qualified to the query, I see deleted items.
> scan \-b myrowid  \-c field/abc:sample_qualifier \-t table <-- returns deleted rows
> After major compaction the problem goes away. 
> {quote}

This message was sent by Atlassian JIRA

View raw message