-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump Spark 3.5.4 RC2 #11731
base: main
Are you sure you want to change the base?
Bump Spark 3.5.4 RC2 #11731
Conversation
the upgrading causes a core dump in iceberg-spark-3.5's tests
|
the failure seems related to arrow minimal reproduce command
|
update: the failure is related to SPARK-50235, and the test passed on Spark 3.5.4 RC1 with reverting that patch |
Please check for some discussion there apache/spark#49131 (comment) |
Yes, I tested it locally and found that after adding a no-op |
@viirya @LuciferYang thank you for the guidance, let me try |
// If a column vector is writable or constant, it should override this method and do nothing. | ||
// See more details at SPARK-50235, SPARK-50463 (Fixed in Spark 3.5.4) | ||
@Override | ||
public void closeIfNotWritable() {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will rename to closeIfFreeable
after RC2 available
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a column vector is writable or constant, it should override this method and do nothing.
we have ConstantColumnVector as well, should we do it vector classes which absolutely requires it ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked the codebase, other vectors overwrite void close() {}
, so they are not affected
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch @pan3793 !
// If a column vector is writable or constant, it should override this method and do nothing. | ||
// See more details at SPARK-50235, SPARK-50463 (Fixed in Spark 3.5.4) | ||
@Override | ||
public void closeIfNotWritable() {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a column vector is writable or constant, it should override this method and do nothing.
we have ConstantColumnVector as well, should we do it vector classes which absolutely requires it ?
FYI @LuciferYang @viirya @dongjoon-hyun @wForget CI is green now, and I think the current Spark |
Thank you for checking Apache Iceberg side, @pan3793 . |
VOTE 3.5.4 RC1 https://lists.apache.org/thread/btdsos7b92962lh10hzswkfy3oj1v0fb
VOTE 3.5.4 RC2 https://lists.apache.org/thread/lttktocm6g6pvhg8zmp37jbhpf51wbyv