camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Corsi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CAMEL-5530) Suggestion to replace HBaseContants class with HBaseConstants interface and other minor changes.
Date Wed, 22 Aug 2012 03:14:38 GMT
Claudio Corsi created CAMEL-5530:
------------------------------------

             Summary: Suggestion to replace HBaseContants class with HBaseConstants interface
and other minor changes.
                 Key: CAMEL-5530
                 URL: https://issues.apache.org/jira/browse/CAMEL-5530
             Project: Camel
          Issue Type: Improvement
          Components: camel-hbase
    Affects Versions: 2.10.0
         Environment: All
            Reporter: Claudio Corsi
            Priority: Minor
             Fix For: 2.10.1, 2.11.0


I was looking at the code and noticed that the HBaseContant class can be an interface since
all of the defined fields can be set within an interface.

I am still trying to understand why the class was called HBaseContant instead of something
like HBaseConstants.  

There are also minors changes that I made that made the code a little consistent with my prior
fix with respect to tablePool.getTable call.

I will include a patch that you can take a look at and decide if these changes are useful
or not.

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

        

Mime
View raw message