Re: [PR] fix(sql): cap parser input length via SQL_MAX_PARSE_LENGTH config [superset]

["sha174n (via GitHub)" <gi...@apache.org>]

sha174n commented on PR #40499:
URL: https://github.com/apache/superset/pull/40499#issuecomment-4694439484

   @rusackas thanks for the review.
   
   On the 1 MB default: typical SQL Lab and dashboard-generated queries are in the kilobytes range, so 1,000,000 bytes leaves wide headroom. It is fully configurable via `SQL_MAX_PARSE_LENGTH`, and setting it to `None` disables the gate, so deployments that legitimately run larger queries (big `IN (...)` lists, large virtual-dataset SQL) can raise or remove it.
   
   Added an UPDATING.md entry in 1eafdc38a9 calling out the cap, the affected paths, and how to adjust it.


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org