You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2013/01/16 18:48:13 UTC

[jira] [Updated] (ACCUMULO-461) Provide convenient mechanism for checking constraints client side

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

Billie Rinaldi updated ACCUMULO-461:
------------------------------------

    Fix Version/s:     (was: 1.5.0)
                   1.6.0
         Assignee:     (was: Billie Rinaldi)

Keith already made the essential fix of checking for bad visibilities in AccumuloFileOutputFormat (ACCUMULO-360).  I'm not planning more than that for 1.5.0.
                
> Provide convenient mechanism for checking constraints client side
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-461
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-461
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: John Vines
>             Fix For: 1.6.0
>
>
> Currently constraints are run on the server side. If the user is running a map reduce which is writing, they may want to make attempts to validate data before writing to make error handling easier. We should provide a generic client mechanism to load a table's constraints and check them before sending them to the batchwriter. 

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