You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "John Vines (Created) (JIRA)" <ji...@apache.org> on 2012/02/16 23:39:01 UTC

[jira] [Created] (ACCUMULO-413) DeleteMany breaks with aggregators/combiners

DeleteMany breaks with aggregators/combiners
--------------------------------------------

                 Key: ACCUMULO-413
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-413
             Project: Accumulo
          Issue Type: Bug
    Affects Versions: 1.3.5
            Reporter: John Vines
            Assignee: John Vines
             Fix For: 1.4.0, 1.3.6


DeleteMany runs an iterator which replaces the Value with NOVALUE because it doesn't make sense to pull back values. This runs at priority 1, so if you have an aggregator expecting things at a level above it, then it could break hard, preventing the deletemany to work. The priority for this iterator should be maxint.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (ACCUMULO-413) DeleteMany breaks with aggregators/combiners

Posted by "John Vines (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACCUMULO-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Vines resolved ACCUMULO-413.
---------------------------------

    Resolution: Fixed
    
> DeleteMany breaks with aggregators/combiners
> --------------------------------------------
>
>                 Key: ACCUMULO-413
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-413
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.3.5
>            Reporter: John Vines
>            Assignee: John Vines
>             Fix For: 1.4.0, 1.3.6
>
>
> DeleteMany runs an iterator which replaces the Value with NOVALUE because it doesn't make sense to pull back values. This runs at priority 1, so if you have an aggregator expecting things at a level above it, then it could break hard, preventing the deletemany to work. The priority for this iterator should be maxint.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira