You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/01/30 17:58:00 UTC
[jira] [Commented] (DRILL-7850) Drill class fails reflection
resulting in ClassNotFoundException
[ https://issues.apache.org/jira/browse/DRILL-7850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275677#comment-17275677 ]
ASF GitHub Bot commented on DRILL-7850:
---------------------------------------
vvysotskyi opened a new pull request #2158:
URL: https://github.com/apache/drill/pull/2158
# [DRILL-7850](https://issues.apache.org/jira/browse/DRILL-7850): Unable to load DrillConnectionImpl class from JDBC driver
## Description
Please refer to https://github.com/jpype-project/jpype/issues/913#issuecomment-767789793 for the problem description.
## Documentation
NA
## Testing
Checked manually.
----------------------------------------------------------------
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
> Drill class fails reflection resulting in ClassNotFoundException
> ----------------------------------------------------------------
>
> Key: DRILL-7850
> URL: https://issues.apache.org/jira/browse/DRILL-7850
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - Java
> Affects Versions: 1.18.0
> Reporter: Karl Nelson
> Assignee: Vova Vysotskyi
> Priority: Major
> Fix For: 1.19.0
>
>
> In a recent issue request on JPype it was reported that Apache Drill fails under JPype. After a bit of tracing it appears that it is not a JPype issue, but something in the Apache Drill jar that is preventing normal Java reflection from operating on the classes in drill. In order for Python to operate on a class it must first probe the class with getMethods. In this case an internal class was returned and when probed it is triggering a Java error. As there isn't much that I can do about internal errors generated by a 3rd party jar, I need to bounce the issue back to the drill developers.
>
> Replication instructions are on the github issue tracker.
> [https://github.com/jpype-project/jpype/issues/913]
>
> Current it is still possible to run Apache Drill with Python as the error can be bypassed by loading the jar file twice. But a recent change to JPype to correct a related issue with unresolved classes will make it a fatal error in the next version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)