jonasbrami opened a new issue, #44599:
URL: https://github.com/apache/doris/issues/44599

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Description
   
   Related to this merge request https://github.com/apache/doris/pull/43281. 
   
   I am afraid of the performance degradation of using Arrow Flight SQL from 
outside the Kubernetes cluster because from my understanding, it would be like 
setting enable_parallel_result_sink = False . Would it be theoretically 
possible, instead of having random BE resolution for the reverse proxy, have a 
smarter reverse proxy that could be, for example, based on path prefix 
(doris-url/be1,  doris-url/be2) ? Then those doris-url/be{i} would become the 
"advertised" urls for the grpc client and would be reachable from outside the 
kubernetes cluster.  Do you think it would be a good idea?
   
   ### Use case
   
   Faster queries when using arrow flight sql from outside Kubernetes cluster
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to