thinkharderdev opened a new pull request #1466:
URL: https://github.com/apache/arrow-datafusion/pull/1466
…v6 addresses
# Which issue does this PR close?
Fixes #1020
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #.
Closes #1020
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
Currently when using Ballista standalone, the standalone executor does not
send its local IP when registering metadata with the scheduler. The scheduler
will default to the IPv4 caller address even though the executor is listening
on the IPv6 loopback address (on some platforms). This will cause clients to
fail to fetch partitions when they try and call the flight service on the IPv4
socket instead of the IPv6 socket.
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
Standalone executor should explicitly return it's local IP address when
registering metadata
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
I don't think so.
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
I don't think so.
--
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]
