You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] When arrow-flight is used and the FE private name name is not resolvable, the client cannot access the FE nodes #62538
I had searched in the issues and found no similar issues.
Version
4.0.5
What's Wrong?
Setup a k8s cluster with FE/BE and add arrow flight ports. You can tell the BE that it has public_host and arrow-flight-proxy-port just fine. But you cannot do the same for the FE. It returns its internal name and redirects the client to that name to pull data (such as from show tables or use mydatabase). For queries that return from BE it runs fine, but not those from FE.
There should be a similar public_host and arrow flight proxy port for the FE, not just the BE.
What You Expected?
A setting in the FE that allows a public host and port to be selected when the driver returns a host for arrow data retrieval. And likely similarly for other URI for web data access.
We're closing this issue because it hasn't been updated in a while.
If you'd like to revive this issue, please reopen it and feel free a maintainer to remove the Stale tag!
Activity
github-actions commentedon Oct 15, 2026
We're closing this issue because it hasn't been updated in a while.
If you'd like to revive this issue, please reopen it and feel free a maintainer to remove the Stale tag!