Github user srowen commented on the issue:
https://github.com/apache/spark/pull/23090
Why not just hard-code a much higher limit? what's the consequence? in a
generic public web server I can see that this defends against malicious or
malformed requests, but that's much less an issue for an internal Spark server.
That is, would a user really need to vary this up and down and know enough
to find this config?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
