[
https://issues.apache.org/jira/browse/DRILL-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577978#comment-17577978
]
ASF GitHub Bot commented on DRILL-8227:
---------------------------------------
jnturton commented on PR #2619:
URL: https://github.com/apache/drill/pull/2619#issuecomment-1210622825
The reason that the snapshot artifact publishing is run inside the existing
checkstyle and protobufs jobs is an attempt at efficiency. Maven will not need
to rebuild all the Drill artifacts since they were just built in the "Build"
step. If this overly eager optimisation and it is preferred to move the
snapshot artifact publishing out to its own job (which is probably more clearly
reported on here in the GH web UI) then let me know...
> JConnect and jTDS JDBC drivers do not implement Connection::getSchema
> ---------------------------------------------------------------------
>
> Key: DRILL-8227
> URL: https://issues.apache.org/jira/browse/DRILL-8227
> Project: Apache Drill
> Issue Type: Bug
> Components: 1.19
> Affects Versions: 1.19.0
> Environment: Apache drill - 1.19.0 , jdk1.8.0_121 , jre1.8.0_121 ,
> Windows 10 Enterprise
> Reporter: Nishanthi
> Assignee: James Turton
> Priority: Major
> Fix For: 1.20.2
>
> Attachments: Sybase_Exception.png, jTDS_Error.png, sqlline_log.png
>
>
> Hi ,
> In Apache drill - 1.19.0 not able to execute a Sybase ASE related query
> getting exception as org.apache.drill.common.exceptions.UserRemoteException:
> SYSTEM ERROR: AbstractMethodError:
> com.sybase.jdbc4.jdbc.SybConnection.getSchema()Ljava/lang/String
> jar - jconn4,
> "driver": "com.sybase.jdbc4.jdbc.SybDriver" ,
> "url": "jdbc:sybase:Tds:?<server-name>:<server-port>/<dbname>"
> Query :
> select * from <storage-plugin-name>.<schema-name>.<table-name>
> Able to execute the query for same configuration with same jar and driver in
> apache drill 1.17.0 but not in apache drill 1.19.0.
> Kindly, look into it as it is coming as a blocker while trying to query with
> sybase ase
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
