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

Bridget Bevens commented on DRILL-6834:
---------------------------------------

Hi [~KazydubB],

I’m planning to add a note to the following pages about the behavior and new 
option:
 * [https://drill.apache.org/docs/interfaces-introduction/]  
 * [https://drill.apache.org/docs/create-table-as-ctas/]  
 * [https://drill.apache.org/docs/create-view/]  
 * [https://drill.apache.org/docs/create-function-using-jar/]  
 * [https://drill.apache.org/docs/drop-function-using-jar/]  
 * [https://drill.apache.org/docs/drop-table/]  
 * [https://drill.apache.org/docs/drop-view/]  
 * [https://drill.apache.org/docs/use/]  
 * [https://drill.apache.org/docs/set/]   

I’m planning to add the following note:

*********************

*NOTE:*

_By default, Drill returns a result set when you issue DDL statements, such as 
CTAS and CREATE VIEW. If the client tool from which you connect to Drill (via 
JDBC) does not expect a result set when you issue DDL statements, set the 
exec.return_result_set_for_ddl option to false, as shown, to prevent the client 
from canceling queries:_

_SET `exec.return_result_set_for_ddl` = false_

_When set to false, Drill returns the affected rows count, and the result set 
is null._  

_***********************_

Please let me know if this is okay, or if I need to make any changes.

Thanks,
Bridget

 ** 

> Introduce option to disable result set for DDL queries 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)

Reply via email to