[jira] [Created] (ACCUMULO-670) BatchWriters do not track Throwables beyond Constraint Violations

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (ACCUMULO-670) BatchWriters do not track Throwables beyond Constraint Violations

JIRA jira@apache.org
John Vines created ACCUMULO-670:
-----------------------------------

             Summary: BatchWriters do not track Throwables beyond Constraint Violations
                 Key: ACCUMULO-670
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-670
             Project: Accumulo
          Issue Type: Bug
          Components: client
    Affects Versions: 1.4.1
            Reporter: John Vines
            Assignee: Billie Rinaldi
             Fix For: 1.5.0


Working on ACCUMULO-259 and adapting the Security Random Walk test to account for cached credentials, to prevent it from crapping out on ambiguous credentials (credentials which are currently propagating). And I noticed that our client side Writers provide no means of feedback to the client if there is a non-ConstraintViolationException.

That is, looking at the TabletServerBatchWriter specifically, we keep track of which servers had errors, which key extents had errors, and what ConstrainViolations we saw, but we don't actually track the actual Throwables we get, aside from ConstraintViolation. We should keep a Collection or Set of the Throwables we see so client code can do proper case checking as well.

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

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (ACCUMULO-670) BatchWriters do not track Throwables beyond Constraint Violations

JIRA jira@apache.org

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

John Vines updated ACCUMULO-670:
--------------------------------

    Issue Type: Improvement  (was: Bug)
   

> BatchWriters do not track Throwables beyond Constraint Violations
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-670
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-670
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.4.1
>            Reporter: John Vines
>            Assignee: Billie Rinaldi
>             Fix For: 1.5.0
>
>
> Working on ACCUMULO-259 and adapting the Security Random Walk test to account for cached credentials, to prevent it from crapping out on ambiguous credentials (credentials which are currently propagating). And I noticed that our client side Writers provide no means of feedback to the client if there is a non-ConstraintViolationException.
> That is, looking at the TabletServerBatchWriter specifically, we keep track of which servers had errors, which key extents had errors, and what ConstrainViolations we saw, but we don't actually track the actual Throwables we get, aside from ConstraintViolation. We should keep a Collection or Set of the Throwables we see so client code can do proper case checking as well.

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

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Assigned] (ACCUMULO-670) BatchWriters do not track Throwables beyond Constraint Violations

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Billie Rinaldi reassigned ACCUMULO-670:
---------------------------------------

    Assignee:     (was: Billie Rinaldi)
   

> BatchWriters do not track Throwables beyond Constraint Violations
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-670
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-670
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.4.1
>            Reporter: John Vines
>             Fix For: 1.5.0
>
>
> Working on ACCUMULO-259 and adapting the Security Random Walk test to account for cached credentials, to prevent it from crapping out on ambiguous credentials (credentials which are currently propagating). And I noticed that our client side Writers provide no means of feedback to the client if there is a non-ConstraintViolationException.
> That is, looking at the TabletServerBatchWriter specifically, we keep track of which servers had errors, which key extents had errors, and what ConstrainViolations we saw, but we don't actually track the actual Throwables we get, aside from ConstraintViolation. We should keep a Collection or Set of the Throwables we see so client code can do proper case checking as well.

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