[
https://issues.apache.org/jira/browse/IMPALA-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485796#comment-17485796
]
Miklos Szurap commented on IMPALA-5550:
---------------------------------------
Impala currently has the following query options:
* a time based limit to protect against runaway queries. see
[EXEC_TIME_LIMIT_S|https://impala.apache.org/docs/build/html/topics/impala_exec_time_limit_s.html]
* row based limit to protect against runaway joins, see
[JOIN_ROWS_PRODUCED_LIMIT|https://impala.apache.org/docs/build/html/topics/impala_join_rows_produced_limit.html]
* row based limit for protect against queries producing too many rows, see
[NUM_ROWS_PRODUCED_LIMIT|https://impala.apache.org/docs/build/html/topics/impala_num_rows_produced_limit.html]
This request should have been addressed by the above (last) query option.
We should close this as a duplicate of IMPALA-8096.
> Session level SET LIMIT in ODBC/JDBC connections
> ------------------------------------------------
>
> Key: IMPALA-5550
> URL: https://issues.apache.org/jira/browse/IMPALA-5550
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Reporter: Ninad Shringarpure
> Priority: Minor
>
> When using Impala in user dashboards like Tableau, users have an ability to
> write custom queries. In some cases when users due to lack of knowledge or
> understanding write bad queries returning, in some cases, billions of rows
> there has to be an ability to safeguard against this.
> A session level setting in ODBC connection provided like SET LIMIT=100000 get
> help limit such issues and accidental resource consumption in the cluster.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
