[
https://issues.apache.org/jira/browse/DRILL-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755564#comment-17755564
]
ASF GitHub Bot commented on DRILL-8436:
---------------------------------------
jnturton commented on PR #2821:
URL: https://github.com/apache/drill/pull/2821#issuecomment-1682344122
I've just set this PR to Draft because I rediscovered a problem in the Drill
JDBC driver. I'll paste a chat message I sent to @vvysotskyi a few months back
below, to reveal the nature of the problem. I'm sure it's ultimately fixable,
but I don't know of an elegant fix yet.
> Hi Vova! I decided to try upgrading Drill's Hadoop libs to 3.3.5. Things
are working but there is a problem in the Drill JDBC fat jar. There, the shade
plugin relocates Hadoop to underneath oadd as usual but now there are class
names present in the core-default.xml file in hadoop-common.jar which are not
updated by the shade plugin. The result is that the JDBC driver is broken.
While the shade plugin can update some kinds of text config files, it doesn't
appear that it can update arbitrary XML config like core-default.xml. I thought
of including our own manually updated copy of core-default.xml in
exec/jdbc-all/src/resources and trying to make sure the shade plugin picks that
one instead of the one in hadoop-common.jar. My only reservation is that
introducing this copy creates a maintenance burden for the future so I thought
to ask you if you have any ideas...
> Upgrade Hadoop 3.2.4 -> 3.3.6
> -----------------------------
>
> Key: DRILL-8436
> URL: https://issues.apache.org/jira/browse/DRILL-8436
> Project: Apache Drill
> Issue Type: Improvement
> Components: library
> Affects Versions: 1.21.1
> Reporter: James Turton
> Assignee: James Turton
> Priority: Minor
> Fix For: 1.22.0
>
>
> Hadoop is upgraded to 3.3.6. Jetty is upgraded to 9.4.51.v20230217.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
