chaoqin-li1123 opened a new pull request, #46651:
URL: https://github.com/apache/spark/pull/46651
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
Fix the python streaming data source timeout issue for large trigger interval
For python streaming source, keep the long running worker archaetecture but
set the socket timeout to be infinity to avoid timeout error.
For python streaming sink, since StreamingWrite is also created per
microbatch in scala side, long running worker cannot be attached to s
StreamingWrite instance. Therefore we abandon the long running worker
architecture, simply call commit() or abort() and exit the worker and allow
spark to reuse worker for us.
### Why are the changes needed?
Currently we run long running python worker process for python streaming
source and sink to perform planning, commit and abort in driver side. Testing
indicate that current implementation cause connection timeout error when
streaming query has large trigger interval.
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
add integration test
### Was this patch authored or co-authored using generative AI tooling?
<!--
If generative AI tooling has been used in the process of authoring this
patch, please include the
phrase: 'Generated-by: ' followed by the name of the tool and its version.
If no, write 'No'.
Please refer to the [ASF Generative Tooling
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
-->
--
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: reviews-unsubscr...@spark.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
