[ https://issues.apache.org/jira/browse/ACCUMULO-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606304#comment-14606304 ]
Josh Elser commented on ACCUMULO-3905: -------------------------------------- That definitely helps. I think that is a very good addition. Would a recommendation to be as specific/thorough as possible when specifying columns be generally applicable? I'm trying to think of a way to best summarize what users would actually need to do. > 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)