You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2013/09/11 21:48:51 UTC

[jira] [Updated] (ACCUMULO-1702) Support "OR instead of AND" option (AND is default) for all Conditions on a ConditionalMutation

     [ https://issues.apache.org/jira/browse/ACCUMULO-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs updated ACCUMULO-1702:
----------------------------------------

    Summary: Support "OR instead of AND" option (AND is default) for all Conditions on a ConditionalMutation  (was: Support OR option instead of AND for all Conditions on a ConditionalMutation)
    
> Support "OR instead of AND" option (AND is default) for all Conditions on a ConditionalMutation
> -----------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-1702
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1702
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Christopher Tubbs
>             Fix For: 1.6.0
>
>
> Currently, ConditionalMutation only supports checking every Condition (AND) for satisfaction. We should be able to satisfy a set of Conditions with an (OR).
> To optimize this (and the AND case), the semantics of adding Conditions to ConditionalMutation should be well-defined, such that the order they are added is preserved. This gives users a way to optimize fast-failure on AND and fast-success on OR, by adding them to the ConditionalMutation in a specific order.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira