You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Daniel Barclay (Drill/MapR) (JIRA)" <ji...@apache.org> on 2015/02/09 19:04:34 UTC

[jira] [Commented] (DRILL-2188) JDBC should default to getting complex data as JSON

    [ https://issues.apache.org/jira/browse/DRILL-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312542#comment-14312542 ] 

Daniel Barclay (Drill/MapR) commented on DRILL-2188:
----------------------------------------------------

> the JDBC driver gets complex data as a complex type which it then converts to JSON.

Which case are you referring to, the case when ResultSet.getString(...) is called or some other case?

In particular, when ResultSet.getObject(...) is called, should we return a JDBC Struct representing a SQL STRUCT type, or something similar?

> JDBC should default to getting complex data as JSON
> ---------------------------------------------------
>
>                 Key: DRILL-2188
>                 URL: https://issues.apache.org/jira/browse/DRILL-2188
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Client - JDBC
>            Reporter: Parth Chandra
>            Assignee: Daniel Barclay (Drill/MapR)
>            Priority: Minor
>             Fix For: 0.9.0
>
>
> Currently the ODBC driver gets complex data as a JSON string while the JDBC driver gets complex data as a complex type which it then converts to JSON. The conversion to JSON in the JDBC path uses an expensive method that also consumes excessive amounts of CPU.
> Since client applications are unable to consume complex data, the default should be to get JSON data and there should be a client side setting (session paramater) to revert to getting  complex data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)