You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/05/02 01:14:16 UTC

[jira] [Commented] (HBASE-7997) One last set of class moves before 0.95 goes out

    [ https://issues.apache.org/jira/browse/HBASE-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647052#comment-13647052 ] 

Sergey Shelukhin commented on HBASE-7997:
-----------------------------------------

This issue is critical and ambiguous. Should it be made less critical, or renamed to "move exception classes to common", or closed due to lack of activity and people can file specific JIRAs if they want to move classes?
                
> One last set of class moves before 0.95 goes out
> ------------------------------------------------
>
>                 Key: HBASE-7997
>                 URL: https://issues.apache.org/jira/browse/HBASE-7997
>             Project: HBase
>          Issue Type: Task
>          Components: Usability
>            Reporter: stack
>            Priority: Critical
>             Fix For: 0.95.1
>
>
> hbase-server depends on hbase-client.  Alot of exceptions are in hbase-client that are thrown by the hbase-server.  Should these be in a common place instead of in hbase-client explicitly?  Say in hbase-common?  The client move put all of our exceptions into an exception package (apparently this is my fault).  Is this a good idea?  How many of these exceptions can we put beside the place where they are thrown?
> This issue is about spending a few hours looking at class locations before 0.95 goes out.
> Any other ideas?

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