bzp2010 commented on PR #11822: URL: https://github.com/apache/apisix/pull/11822#issuecomment-2676381076
I don't think it's a good idea to just do dirty patches like this on the route spec. If it is ok to extend the limit values, then the same thing should be done for all resources. It's arguable that such a restriction might only be done due to some “inertia” on the part of the API creators to follow what they've done before, which might not really be necessary or justified. The length of the value is meaningless in terms of functionality, and may only affect the speed of etcd synchronization and the amount of memory used by APISIX when large strings are used. Perhaps you could start a discussion to expand the value on all resources. Or perhaps the limit could be moved to a configuration file and allow the user to define it at runtime without modifying the code. What do others think? -- 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]
