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 Mon, 29 Jun 2015 20:06:05 GMT


Keith Turner commented on ACCUMULO-3905:

It could impact a row filter that fetches more columns inorder to decided if a row is visible.

Would adding something like the following help?

For example assume fetchColumns(A, Q1) and fetchColumns(B,Q1) is called on a scanner and a
custom iterator is configured.  The families (A,B) will be passed to the seek method of the
customn iterator.  If the custom iterator seeks its source iterator using the families (A,B,C),
it will never see any data from C because the system iterator filtering A:Q1 and B:Q1 will
prevent the C family from getting through.

> RowDeletingIterator does not work if columns are specified
> ----------------------------------------------------------
>                 Key: ACCUMULO-3905
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Eric Newton
>            Assignee: Keith Turner
>             Fix For: 1.6.4, 1.7.1, 1.8.0
>         Attachments: ACCUMULO-3905-1.patch
> (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