clintropolis commented on issue #17769: URL: https://github.com/apache/druid/issues/17769#issuecomment-2770918710
Any reason not to just allow requests to contain `SET` statements to be included prior to a insert/replace/select statement? that seems to solve the problem of needing things prior to planning the insert/replace/select because we could parse them individually and build up the context before planning. Like allow the request to contain something like: ``` SET maxNumTasks 8; REPLACE INTO wikipedia2 OVERWRITE ALL SELECT * FROM wikipedia ``` or: ``` SET enableParallelMerge false; SET sqlOuterLimit 10; SELECT * FROM wikipedia ``` This syntax is used by lots of other databases too: https://learn.microsoft.com/en-us/sql/t-sql/statements/set-statements-transact-sql?view=sql-server-ver16 https://www.postgresql.org/docs/current/sql-set.html https://dev.mysql.com/doc/refman/8.4/en/set-statement.html https://docs.pinot.apache.org/users/user-guide-query/query-options#set-statement https://clickhouse.com/docs/sql-reference/statements/set https://docs.vertica.com/23.3.x/en/sql-reference/statements/set-statements/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
