[
https://issues.apache.org/jira/browse/DRILL-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312748#comment-14312748
]
Parth Chandra commented on DRILL-2188:
--------------------------------------
See https://issues.apache.org/jira/browse/DRILL-836. This added a new flag in
UserToBitHandshake support_complex_types to allow a client to specifically ask
for complex data. The JDBC driver asks for complex data. The ODBC driver does
not ask for complex data and gets back JSON instead.
For JDBC we would like to default to asking for JSON data, but also allow a
session parameter that allows the JDBC driver to ask for complex data instead.
> 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)
