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

Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2018/12/12 17:55:34 UTC

[GitHub] keith-turner opened a new issue #824: Refactor how constraint violations are handled

keith-turner opened a new issue #824: Refactor how constraint violations are handled
URL: https://github.com/apache/accumulo/issues/824
 
 
   [Tablet 
    server code](https://github.com/apache/accumulo/blob/c8d19d45f361f49a4d42b07310393b7bdf68b3b4/server/tserver/src/main/java/org/apache/accumulo/tserver/TabletServer.java#L1059) that handles contraint violation uses an exception to return information about constraint violations.  I am not sure about this, but I think it may clean up the code if an exception was not used to return information in this way.  The code could instead always return an object contains info about 0 or more constraint violations.  I think this could cut down on duplicate code, how that may not be the case.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services