camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Corsi (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5506) HBase component does not extract that table name in all cases and HBase runtime version issues.
Date Wed, 15 Aug 2012 14:08:38 GMT


Claudio Corsi commented on CAMEL-5506:

The pom.xml update is only required for users that have a maven project and want to test using
camel:run against an already running hbase system.  If the service is using 0.92.x or greater,
then the camel:run will produce the illegal argument exception with the not a host:port pair.
 Adding the above update to their maven project pom file will resolve that issue.

The original patch that includes changing the hbase to provided is not required in general
since the api using the 0.90.5 hbase is the same as the latest version of hbase.

> HBase component does not extract that table name in all cases and HBase runtime version
> -----------------------------------------------------------------------------------------------
>                 Key: CAMEL-5506
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.10.0
>         Environment: Any
>            Reporter: Claudio Corsi
>              Labels: camel-hbase
>             Fix For: 2.10.1, 2.11.0
>         Attachments: hbase.diffs
> The current hbase component uses the URI getHost method to retrieve the table name but
this method returns null if the host name does not conform to the requirements of this method.
 For instance, it should include a '.' in the name, or is a ipv4 or ipv6 valid address string.
 If the table name is a simple name then the getHost method will return null instead of the
name of the table.  This will in turn cause a NPE exception.
> The other issue is that if you are using 0.92.x or greater with the current implementation
of the camel-hbase component.  An IllegalArgumentException is generated because of an incompatible
host:port pair.  This is caused by the fact that the current hbase integration uses 0.90.5
and this will conflict with those versions.
> I have a patch that solves both issues but in the second case.  It will require that
the user define the specific hbase client version that they need to use.
> btw, the camel-hbase component is not available as an option for the Component/s drop
down list.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message