[fix](arrow-flight-sql) Fix Arrow Flight bind wrong Host in Fqdn #34850
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
Contributor
Author
|
run buildall |
yiguolei
approved these changes
May 15, 2024
Contributor
|
PR approved by at least one committer and no changes requested. |
github-actions
bot
added
approved
Contributor
|
PR approved by anyone and no changes requested. |
yiguolei
pushed a commit
that referenced
this pull request
May 15, 2024
3 tasks
xinyiZzz
added a commit
that referenced
this pull request
Sep 1, 2024
… error `0.0.0.0:xxx, connection refused` (#40002) Fix: #36340 Introduced in: #34850 ``` adbc_driver_manager.OperationalError: IO: [FlightSQL] connection error: desc = "transport: Error while dialing: dial tcp 0.0.0.0:8029: connect: connection refused" (Unavailable; DoGet: endpoint 0: [uri:"grpc+tcp://0.0.0.0:8029"]) ``` When query results are returned from FE Arrow Flight server, and Doris FE and ADBC Client are not on the same machine, such as `show tables;`, `show databases;`, the IP in FlightInfo returned by FE to the client is wrong, and `0.0.0.0` is returned instead of the real IP of FE. The client fails to pull the results from `0.0.0.0`. No problem when query results are returned from BE Arrow Flight server, such as the normal query statement `select * from xxx`.
xinyiZzz
added a commit
to xinyiZzz/incubator-doris
that referenced
this pull request
Sep 1, 2024
… error `0.0.0.0:xxx, connection refused` (apache#40002) Fix: apache#36340 Introduced in: apache#34850 ``` adbc_driver_manager.OperationalError: IO: [FlightSQL] connection error: desc = "transport: Error while dialing: dial tcp 0.0.0.0:8029: connect: connection refused" (Unavailable; DoGet: endpoint 0: [uri:"grpc+tcp://0.0.0.0:8029"]) ``` When query results are returned from FE Arrow Flight server, and Doris FE and ADBC Client are not on the same machine, such as `show tables;`, `show databases;`, the IP in FlightInfo returned by FE to the client is wrong, and `0.0.0.0` is returned instead of the real IP of FE. The client fails to pull the results from `0.0.0.0`. No problem when query results are returned from BE Arrow Flight server, such as the normal query statement `select * from xxx`.
dataroaring
pushed a commit
that referenced
this pull request
Oct 9, 2024
… error `0.0.0.0:xxx, connection refused` (#40002) Fix: #36340 Introduced in: #34850 ``` adbc_driver_manager.OperationalError: IO: [FlightSQL] connection error: desc = "transport: Error while dialing: dial tcp 0.0.0.0:8029: connect: connection refused" (Unavailable; DoGet: endpoint 0: [uri:"grpc+tcp://0.0.0.0:8029"]) ``` When query results are returned from FE Arrow Flight server, and Doris FE and ADBC Client are not on the same machine, such as `show tables;`, `show databases;`, the IP in FlightInfo returned by FE to the client is wrong, and `0.0.0.0` is returned instead of the real IP of FE. The client fails to pull the results from `0.0.0.0`. No problem when query results are returned from BE Arrow Flight server, such as the normal query statement `select * from xxx`.
xinyiZzz
added a commit
to xinyiZzz/incubator-doris
that referenced
this pull request
Nov 11, 2024
… error `0.0.0.0:xxx, connection refused` (apache#40002) Fix: apache#36340 Introduced in: apache#34850 ``` adbc_driver_manager.OperationalError: IO: [FlightSQL] connection error: desc = "transport: Error while dialing: dial tcp 0.0.0.0:8029: connect: connection refused" (Unavailable; DoGet: endpoint 0: [uri:"grpc+tcp://0.0.0.0:8029"]) ``` When query results are returned from FE Arrow Flight server, and Doris FE and ADBC Client are not on the same machine, such as `show tables;`, `show databases;`, the IP in FlightInfo returned by FE to the client is wrong, and `0.0.0.0` is returned instead of the real IP of FE. The client fails to pull the results from `0.0.0.0`. No problem when query results are returned from BE Arrow Flight server, such as the normal query statement `select * from xxx`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
If use Fqdn, FE Host will use hostname. then will use hostname and port creating Arrow Flight Server, If
/etc/hostsis configured with an intranet IP, Arrow Flight Server will bind intranet IP, external network inaccessible.so, let Arrow Flight Server bind
0.0.0.0, allowing all IPs to access.In addition, fix Arrow Flight connection calling getMysqlChannel().
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...