Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 29 Jun 2015 20:07:06 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12838483.1434550143000.48919.1435608426056@Atlassian.JIRA>
In-Reply-To: <JIRA.12838483.1434550143000@Atlassian.JIRA>
References: <JIRA.12838483.1434550143000@Atlassian.JIRA>
 <JIRA.12838483.1434550143964@arcas>
Subject: [jira] [Comment Edited] (ACCUMULO-3905) RowDeletingIterator does
 not work if columns are specified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606285#comment-14606285 ] 

Keith Turner edited comment on ACCUMULO-3905 at 6/29/15 8:06 PM:
-----------------------------------------------------------------

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?

{noformat}
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.
{noformat}


was (Author: kturner):
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?

{noformat}
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.
{noformat}


> 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)