You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2012/08/21 03:48:38 UTC

[jira] [Assigned] (SMX4-1185) HBase bundle needs some tuning on imports

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

Jean-Baptiste Onofré reassigned SMX4-1185:
------------------------------------------

    Assignee: Jean-Baptiste Onofré
    
> HBase bundle needs some tuning on imports
> -----------------------------------------
>
>                 Key: SMX4-1185
>                 URL: https://issues.apache.org/jira/browse/SMX4-1185
>             Project: ServiceMix 4
>          Issue Type: Bug
>          Components: Bundles
>            Reporter: Ioannis Canellos
>            Assignee: Jean-Baptiste Onofré
>
> Unfortunately hbase provides a single artifact for all cases. That artifact contains both server and client side packages. Especially on the client side there are 4 different client interfaces.
> I think that most of the imports should be marked as optional. For example:
> protobuf, avro and thrift are refering to client interfaces that are optional.
> I think that the same applies to packages like joptsimple, paranamer etc, which are related to cli stuff.
> Finally, zooekeeper and hadoop shouldn't be optional as I can't think of any use case that doesn't involve those two.
> Camel provides a minimalistic camel-hbase feature that could serve on narrowing down that required imports. This is of course not a panacea but its definitly more minimal than what we have already.

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