[SPARK-46400][CORE][SQL][3.5] When there are corrupted files in the local maven repo, skip this cache and try again #45017
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
…ocal maven repo, skip this cache and try again
LuciferYang
approved these changes
Feb 8, 2024
LuciferYang
pushed a commit
that referenced
this pull request
Feb 8, 2024
…ocal maven repo, skip this cache and try again ### What changes were proposed in this pull request? The pr aims to - fix potential bug(ie: #44208) and enhance user experience. - make the code more compliant with standards Backport above to branch 3.5. Master branch pr: #44343 ### Why are the changes needed? We use the local maven repo as the first-level cache in ivy. The original intention was to reduce the time required to parse and obtain the ar, but when there are corrupted files in the local maven repo,The above mechanism will be directly interrupted and the prompt is very unfriendly, which will greatly confuse the user. Based on the original intention, we should skip the cache directly in similar situations. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manually test. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #45017 from panbingkun/branch-3.5_SPARK-46400. Authored-by: panbingkun <[email protected]> Signed-off-by: yangjie01 <[email protected]>
Contributor
|
Merged into branch-3.5. Thanks @panbingkun |
Member
|
Please update the JIRA for the backporting PRs, @LuciferYang . 😄 |
dongjoon-hyun
pushed a commit
that referenced
this pull request
Feb 22, 2024
…E_VERSIONS` ### What changes were proposed in this pull request? This pr aims to remove `3.5.1` from `SKIP_SPARK_RELEASE_VERSIONS(build_maven.yml)` to restore test of `HiveExternalCatalogVersionsSuite` using maven with Spark 3.5.x. ### Why are the changes needed? SPARK-46400 | #45017 has already merged into Spark 3.5.1, and the corresponding issue no longer exists for Spark 3.5.1 + ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Monitor maven daily test after merged. ### Was this patch authored or co-authored using generative AI tooling? NO Closes #45217 from LuciferYang/SPARK-47127-FOLLOWUP. Authored-by: yangjie01 <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
ericm-db
pushed a commit
to ericm-db/spark
that referenced
this pull request
Mar 5, 2024
…E_VERSIONS` ### What changes were proposed in this pull request? This pr aims to remove `3.5.1` from `SKIP_SPARK_RELEASE_VERSIONS(build_maven.yml)` to restore test of `HiveExternalCatalogVersionsSuite` using maven with Spark 3.5.x. ### Why are the changes needed? SPARK-46400 | apache#45017 has already merged into Spark 3.5.1, and the corresponding issue no longer exists for Spark 3.5.1 + ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Monitor maven daily test after merged. ### Was this patch authored or co-authored using generative AI tooling? NO Closes apache#45217 from LuciferYang/SPARK-47127-FOLLOWUP. Authored-by: yangjie01 <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
dongjoon-hyun
pushed a commit
that referenced
this pull request
Aug 14, 2024
…ERSIONS` ### What changes were proposed in this pull request? The pr aims to remove `3.4.2` from `SKIP_SPARK_RELEASE_VERSIONS(build_maven.yml)`. ### Why are the changes needed? - Why was `SKIP_SPARK_RELEASE_VERSIONS` introduced? See here: https://issues.apache.org/jira/browse/SPARK-46400 - [SPARK-46400](#45017) has already merged into Spark `3.4.3`, and the corresponding issue no longer exists for Spark `3.4.3+` - The following location only includes `the version` we have `fixed` for this issue https://dist.apache.org/repos/dist/release/spark/ <img width="433" alt="image" src="https://github.com/user-attachments/assets/bfdf8bca-b972-490a-bc19-cb95eb83a352"> ### Does this PR introduce _any_ user-facing change? No, only for GA's tests. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #47748 from panbingkun/SPARK-49232. Authored-by: panbingkun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
IvanK-db
pushed a commit
to IvanK-db/spark
that referenced
this pull request
Sep 20, 2024
…ERSIONS` ### What changes were proposed in this pull request? The pr aims to remove `3.4.2` from `SKIP_SPARK_RELEASE_VERSIONS(build_maven.yml)`. ### Why are the changes needed? - Why was `SKIP_SPARK_RELEASE_VERSIONS` introduced? See here: https://issues.apache.org/jira/browse/SPARK-46400 - [SPARK-46400](apache#45017) has already merged into Spark `3.4.3`, and the corresponding issue no longer exists for Spark `3.4.3+` - The following location only includes `the version` we have `fixed` for this issue https://dist.apache.org/repos/dist/release/spark/ <img width="433" alt="image" src="https://github.com/user-attachments/assets/bfdf8bca-b972-490a-bc19-cb95eb83a352"> ### Does this PR introduce _any_ user-facing change? No, only for GA's tests. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#47748 from panbingkun/SPARK-49232. Authored-by: panbingkun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
attilapiros
pushed a commit
to attilapiros/spark
that referenced
this pull request
Oct 4, 2024
…ERSIONS` ### What changes were proposed in this pull request? The pr aims to remove `3.4.2` from `SKIP_SPARK_RELEASE_VERSIONS(build_maven.yml)`. ### Why are the changes needed? - Why was `SKIP_SPARK_RELEASE_VERSIONS` introduced? See here: https://issues.apache.org/jira/browse/SPARK-46400 - [SPARK-46400](apache#45017) has already merged into Spark `3.4.3`, and the corresponding issue no longer exists for Spark `3.4.3+` - The following location only includes `the version` we have `fixed` for this issue https://dist.apache.org/repos/dist/release/spark/ <img width="433" alt="image" src="https://github.com/user-attachments/assets/bfdf8bca-b972-490a-bc19-cb95eb83a352"> ### Does this PR introduce _any_ user-facing change? No, only for GA's tests. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#47748 from panbingkun/SPARK-49232. Authored-by: panbingkun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
himadripal
pushed a commit
to himadripal/spark
that referenced
this pull request
Oct 19, 2024
…ERSIONS` ### What changes were proposed in this pull request? The pr aims to remove `3.4.2` from `SKIP_SPARK_RELEASE_VERSIONS(build_maven.yml)`. ### Why are the changes needed? - Why was `SKIP_SPARK_RELEASE_VERSIONS` introduced? See here: https://issues.apache.org/jira/browse/SPARK-46400 - [SPARK-46400](apache#45017) has already merged into Spark `3.4.3`, and the corresponding issue no longer exists for Spark `3.4.3+` - The following location only includes `the version` we have `fixed` for this issue https://dist.apache.org/repos/dist/release/spark/ <img width="433" alt="image" src="https://github.com/user-attachments/assets/bfdf8bca-b972-490a-bc19-cb95eb83a352"> ### Does this PR introduce _any_ user-facing change? No, only for GA's tests. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#47748 from panbingkun/SPARK-49232. Authored-by: panbingkun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
turboFei
pushed a commit
to turboFei/spark
that referenced
this pull request
Nov 6, 2025
…ocal maven repo, skip this cache and try again (apache#367) ### What changes were proposed in this pull request? The pr aims to - fix potential bug(ie: apache#44208) and enhance user experience. - make the code more compliant with standards Backport above to branch 3.5. Master branch pr: apache#44343 ### Why are the changes needed? We use the local maven repo as the first-level cache in ivy. The original intention was to reduce the time required to parse and obtain the ar, but when there are corrupted files in the local maven repo,The above mechanism will be directly interrupted and the prompt is very unfriendly, which will greatly confuse the user. Based on the original intention, we should skip the cache directly in similar situations. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manually test. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#45017 from panbingkun/branch-3.5_SPARK-46400. Authored-by: panbingkun <[email protected]> Signed-off-by: yangjie01 <[email protected]> Co-authored-by: panbingkun <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What changes were proposed in this pull request?
The pr aims to
Backport above to branch 3.5.
Master branch pr: #44343
Why are the changes needed?
We use the local maven repo as the first-level cache in ivy. The original intention was to reduce the time required to parse and obtain the ar, but when there are corrupted files in the local maven repo,The above mechanism will be directly interrupted and the prompt is very unfriendly, which will greatly confuse the user. Based on the original intention, we should skip the cache directly in similar situations.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually test.
Was this patch authored or co-authored using generative AI tooling?
No.