You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/08/27 12:30:36 UTC
[GitHub] [camel-quarkus] ppalaga opened a new issue #1648: HBase native support
ppalaga opened a new issue #1648:
URL: https://github.com/apache/camel-quarkus/issues/1648
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #1648: HBase native support
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1648:
URL: https://github.com/apache/camel-quarkus/issues/1648#issuecomment-728215788
The shaded Netty is version 3.x and in addition to that there is Netty 4.x in the client class path. Therefore the unshading trick we applied in #2008 won't work here.
I tied with trial and error strategy a bit, but did not come too far without understanding the hbase client internals. Here is my last state: https://github.com/ppalaga/camel-quarkus/tree/i1648.2
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #1648: HBase support
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1648:
URL: https://github.com/apache/camel-quarkus/issues/1648#issuecomment-707344481
The native mode is partly finished in #1906, I gave up when I found out that HBase has a shaded Netty.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #1648: HBase support
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1648:
URL: https://github.com/apache/camel-quarkus/issues/1648#issuecomment-682025059
Even a JVM extension is hard to do due to dependency alignment issues and due to the fact that there is no way to configure the component not to connect to the cluster at startup. Here my today's attempt that basically works, but is not good enough to be merged: https://github.com/ppalaga/camel-quarkus/commit/f2401f3feb8563b80b3b72a739b206fdd7017b61
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #1648: HBase support
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1648:
URL: https://github.com/apache/camel-quarkus/issues/1648#issuecomment-707024768
The dependency hell was not that bad after all, at least the extension part - so I solved it with the usual means. The test module was a bit worse due to the mess in the transitive dependencies of `hbase-testing-util` (used to start the test cluster). For that one, was able to keep dependencyManagement config in the test module.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org