[
https://issues.apache.org/jira/browse/DRILL-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bohdan Kazydub updated DRILL-6834:
----------------------------------
Summary: Introduce option to disable result set for CTAS, CREATE VIEW,
CREATE FUNCTION, DROP TABLE, DROP VIEW, DROP FUNCTION, USE schema, SET option,
REFRESH METADATA TABLE for JDBC connection (was: Introduce option to disable
result set on CTAS, create view and drop table/view etc. for JDBC connection)
> Introduce option to disable result set for CTAS, CREATE VIEW, CREATE
> FUNCTION, DROP TABLE, DROP VIEW, DROP FUNCTION, USE schema, SET option,
> REFRESH METADATA TABLE for JDBC connection
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DRILL-6834
> URL: https://issues.apache.org/jira/browse/DRILL-6834
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Bohdan Kazydub
> Assignee: Bohdan Kazydub
> Priority: Major
> Labels: doc-impacting, ready-to-commit
> Fix For: 1.15.0
>
>
> There are some tools (Unica, dBeaver, TalenD) that do not expect to obtain
> result set on CTAS query. As a result the query gets canceled. Hive, on the
> other hand, does not return result set for the query and these tools work
> well.
> To improve Drill's integration with such tools a session option
> {{`exec.return_result_set_for_ddl}}{{`}} is introduced. If the option is
> enabled (set to `true`) Drill's behaviour will be unchanged, i.e. a result
> set will be returned for all queries. If the option is disabled (set to
> `false`), CTAS, CREATE VIEW, CREATE FUNCTION, DROP TABLE, DROP VIEW, DROP
> FUNCTION, USE schema, SET option, REFRESH METADATA TABLE queries will not
> return result set but {{updateCount}} instead.
> The option affects JDBC connections only.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
