[
https://issues.apache.org/jira/browse/DRILL-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Nadeau resolved DRILL-167.
----------------------------------
Resolution: Fixed
Merged in 651b3e9 and preceding
> Enable full engine in JDBC Layer
> --------------------------------
>
> Key: DRILL-167
> URL: https://issues.apache.org/jira/browse/DRILL-167
> Project: Apache Drill
> Issue Type: New Feature
> Reporter: Jacques Nadeau
> Assignee: Jacques Nadeau
> Priority: Minor
>
> You can get to the full exec engine now but too many things are implicitly
> defined. Instead, we need to add explicit options.
> My proposal is to define a set of jdbc connection string properties:
> engine=ref means that the Reference interpreter's capabilities and schemas
> are available. engine=full (default) means that the full execution engines
> tools should be available. engine=both means that both types are available.
> For engine=full.
> We will have the additional property: zk=[connection string]
> This also requires the implementation of a smarter Schema type that provides
> automatic schema for all types recognized by the execution engine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
