hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-7997) One last set of class moves before 0.95 goes out
Date Wed, 08 May 2013 20:45:17 GMT

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

stack resolved HBASE-7997.

    Resolution: Won't Fix

Played w/ structure101 for a while.  Packages are reaching over into each other -- everything
references pb and util packages -- but saw no easy wins other than the unused files it spotlighted.
 Going to close this as won't fix for 0.95.1
> 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
>             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
> 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

View raw message