[WIP] showacase PR - strange spark behaviour#11891
Closed
homar wants to merge 1 commit intotrinodb:masterfrom
Closed
[WIP] showacase PR - strange spark behaviour#11891homar wants to merge 1 commit intotrinodb:masterfrom
homar wants to merge 1 commit intotrinodb:masterfrom
Conversation
homar
force-pushed
the
homar/spark_caches_stuff_iceberg
branch
from
93533c3 to
db1bae9
Compare
homar
force-pushed
the
homar/spark_caches_stuff_iceberg
branch
2 times, most recently
from
6ef33c3 to
c70f037
Compare
homar
force-pushed
the
homar/spark_caches_stuff_iceberg
branch
from
c70f037 to
dc6c458
Compare
Member
Author
|
I am closing this one as its only purpose was to demonstrate strange behaviour that was caused by spark caching metadata internally |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
DO NOT MERGE
Strange spark behaviour:
testSparkDoesntReadTrinoTableWithDeletes- fails because spark doesn't see updates made by trino after it performs a deletetestSparkReadsTrinoTableWithDeletes- doesn't fail, the difference is that updates after delete are made by spark.It looks like spark caches something internally. It has bad implications as it will make operations like optimize, delete_orphan_files and expire_snapshots break future queries from spark
Related issues, pull requests, and links
Documentation
( ) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
( ) No release notes entries required.
( ) Release notes entries required with the following suggested text: