[
https://issues.apache.org/jira/browse/ACCUMULO-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606255#comment-14606255
]
Josh Elser commented on ACCUMULO-3905:
--------------------------------------
Documentation change for 1.6 and 1.7 makes sense, so +1 to that approach.
Reading the documentation changes, I.. can't really say it helps me understand
the problem. The only clear thing I can grok from the updates is that
"Iterators can change the columns fetched during seek()", but it doesn't seem
like a clear reason as to me why the RowDeletingIterator doesn't work.
I don't have a good suggestion on how to improve it though. Ultimately, users
will need to explicitly provide the columns they want to fetch in certain
cases, right? While it could affect any iterator, a common case is the
RowDeletingIterator. Are there more that we package?
> RowDeletingIterator does not work if columns are specified
> ----------------------------------------------------------
>
> Key: ACCUMULO-3905
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3905
> 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, e.g.
> 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
(v6.3.4#6332)
