DaltonModlin opened a new issue, #418:
URL: https://github.com/apache/arrow-ballista/issues/418

   **Is your feature request related to a problem or challenge? Please describe 
what you are trying to do.**
   We have the ability to proxy flights through the Scheduler, but whether or 
not the client tries to get the Flight from the Scheduler or the Executor is 
entirely up to us and the IP address we advertise as having the Flight.
   
   Many deployments will be made easier if we provide the ability to proxy all 
flights through the Scheduler. However, some users may prefer the ability to 
have the Client retrieve flights directly from Executors, so a flag seems like 
the appropriate middle ground.
   
   **Describe the solution you'd like**
   Since there are two potential modes of operation, we should use command line 
flags (or environment variables) to determine which mode to use. Currently, the 
executor has command line arguments called `--bind-host` and `--external-host`. 
Following this pattern, this issue proposes we add a command line argument to 
the scheduler called --advertise-host. If specified, all Flights will be 
altered to use that address. If not specified, the IPs of the executors will be 
left intact.
   
   **Describe alternatives you've considered**
   - Force everyone to proxy via the Scheduler
   - Don't ever proxy through the Scheduler
   
   **Additional context**
   Add any other context or screenshots about the feature request here.


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

Reply via email to