You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/11/02 14:39:51 UTC

[GitHub] [arrow-ballista] avantgardnerio commented on pull request #472: Add SchedulerConfig for the scheduler configurations, like event_loop_buffer_size, finished_job_data_clean_up_interval_seconds, finished_job_state_clean_up_interval_seconds

avantgardnerio commented on PR #472:
URL: https://github.com/apache/arrow-ballista/pull/472#issuecomment-1300556297

   > advertise-flight-result-endpoint
   
   How about `--advertise-flightsql-endpoint`, which should remove any ambiguity as this is only related to FlightSQL, not regular flights between clients?
   
   A tangent not for this PR: we probably just want separate `--advertise-host` and `--flightsql-port` at some point, as I imagine other services may eventually need to know what host is listening. And now that I think about it, we shouldn't need the port to be specified as that shouldn't get remapped by anything.


-- 
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: github-unsubscribe@arrow.apache.org

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