You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Karl Nelson (Jira)" <ji...@apache.org> on 2021/01/26 02:36:00 UTC

[jira] [Created] (DRILL-7850) Drill class fails reflection resulting in ClassNotFoundException

Karl Nelson created DRILL-7850:
----------------------------------

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


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)