[
https://issues.apache.org/jira/browse/DRILL-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944102#comment-14944102
]
Daniel Barclay (Drill) commented on DRILL-2528:
-----------------------------------------------
Also, we've stopped using ProGuard for the JDBC-all Jar file.
> Drill-JDBC-All Jar uses outdated classes
> ----------------------------------------
>
> Key: DRILL-2528
> URL: https://issues.apache.org/jira/browse/DRILL-2528
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
> Affects Versions: 0.8.0
> Environment: RHEL 6.4
> Reporter: Kunal Khatua
> Assignee: DrillCommitter
> Fix For: 1.0.0
>
> Attachments: DRILL-2582.1.patch.txt
>
>
> Since the DrillResultSet.getQueryId() method was unavailable when using the
> Drill-JDBC-All jar, I originally thought there were multiple copies of the
> DrillResultSet class within the code base, but I see only one in GitHub.
> However, when decompiling the two JDBC jar files, the drill-jdbc-all...jar
> shows missing elements within the DrillResultSet class.
> The build creation process is using outdated source code (or dependencies),
> as the following is missing in the DrillResultSet class
> import org.apache.drill.exec.proto.helper.QueryIdHelper;
> public String getQueryId() {
> if (this.queryId != null) {
> return QueryIdHelper.getQueryId(this.queryId);
> }
> return null;
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
