[
https://issues.apache.org/jira/browse/DRILL-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580184#comment-17580184
]
ASF GitHub Bot commented on DRILL-8279:
---------------------------------------
vvysotskyi commented on PR #2622:
URL: https://github.com/apache/drill/pull/2622#issuecomment-1216365721
@luocooong, Drill plugins are still pluggable, so you can provide your own
implementations if you need.
Phoenix official connectors [1] for such big data tools like Spark, Hive and
Pig also use thick client, so such decision should be production-suitable. By
the way I didn't find official connectors that use thin client in that
repository.
Ideally, if Phoenix thin client shades some libraries, it should also
relocate them to avoid such issues. I don't see any other correct way for
resolving this class path conflict in other way. Creating specific module and
repacking Phoenix there when building Drill is overhead, and didn't guarantee
that nothing would be broken. Having custom repo that provides relocated
classes also not good decision since it will make more complex supporting new
Phoenix versions.
[1] https://github.com/apache/phoenix-connectors
> Use thick Phoenix driver
> ------------------------
>
> Key: DRILL-8279
> URL: https://issues.apache.org/jira/browse/DRILL-8279
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Vova Vysotskyi
> Assignee: Vova Vysotskyi
> Priority: Blocker
>
> phoenix-queryserver-client shades Avatica classes, so it causes issues when
> starting Drill and shaded class from phoenix jars is loaded before, so Drill
> wouldn't be able to start correctly.
> To avoid that, phoenix thick client can be used, it also will improve query
> performance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
