forked from theopenlab/spark
-
Notifications
You must be signed in to change notification settings - Fork 1
[Shift] return self.copy during shift with period == 0 #4
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
Open
bzhaoopenstack
wants to merge
5
commits into
master
Choose a base branch
from
period
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
### What changes were proposed in this pull request? This PR aims to upgrade Apache Kafka to 3.2.1. ### Why are the changes needed? Apache Kafka 3.2.1 is released. - https://lists.apache.org/thread/b6nonzos2qjhc9tpolld9qxrcxqcg011 Apache Kafka 3.2.1 has the following patches. - https://home.apache.org/~davidarthur/kafka-3.2.1-rc3/RELEASE_NOTES.html [KAFKA-14013](https://issues.apache.org/jira/browse/KAFKA-14013) Limit the length of the `reason` field sent on the wire Bug [KAFKA-13474](https://issues.apache.org/jira/browse/KAFKA-13474) Regression in dynamic update of broker certificate [KAFKA-13572](https://issues.apache.org/jira/browse/KAFKA-13572) Negative value for 'Preferred Replica Imbalance' metric [KAFKA-13773](https://issues.apache.org/jira/browse/KAFKA-13773) Data loss after recovery from crash due to full hard disk [KAFKA-13861](https://issues.apache.org/jira/browse/KAFKA-13861) validateOnly request field does not work for CreatePartition requests in Kraft mode. [KAFKA-13899](https://issues.apache.org/jira/browse/KAFKA-13899) Inconsistent error codes returned from AlterConfig APIs [KAFKA-13998](https://issues.apache.org/jira/browse/KAFKA-13998) JoinGroupRequestData 'reason' can be too large [KAFKA-14010](https://issues.apache.org/jira/browse/KAFKA-14010) alterISR request won't retry when receiving retriable error [KAFKA-14024](https://issues.apache.org/jira/browse/KAFKA-14024) Consumer stuck during cooperative rebalance for Commit offset in onJoinPrepare [KAFKA-14035](https://issues.apache.org/jira/browse/KAFKA-14035) QuorumController handleRenounce throws NPE [KAFKA-14055](https://issues.apache.org/jira/browse/KAFKA-14055) Transaction markers may be lost during cleaning if data keys conflict with marker keys [KAFKA-14062](https://issues.apache.org/jira/browse/KAFKA-14062) OAuth client token refresh fails with SASL extensions [KAFKA-14079](https://issues.apache.org/jira/browse/KAFKA-14079) Source task will not commit offsets and develops memory leak if "error.tolerance" is set to "all" ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the CIs Closes apache#37261 from dongjoon-hyun/SPARK-39848. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
…rithmetic overflow ### What changes were proposed in this pull request? Similar with apache#37313, currently, when arithmetic overflow errors happen under ANSI mode, the error messages are like ``` [ARITHMETIC_OVERFLOW] long overflow. Use 'try_multiply' to tolerate overflow and return NULL instead. If necessary set spark.sql.ansi.enabled to "false" ``` The "(except for ANSI interval type)" part is confusing. We should remove it for the numeric arithmetic operations and have a new error class for the interval division error: `INTERVAL_ARITHMETIC_OVERFLOW` ### Why are the changes needed? For better error messages ### Does this PR introduce _any_ user-facing change? Yes, Use different error classes for arithmetic overflows of numeric/interval.. After changes, the error messages are simpler and more clear. ### How was this patch tested? UT Closes apache#37337 from gengliangwang/improveOverflowMsg. Authored-by: Gengliang Wang <gengliang@apache.org> Signed-off-by: Gengliang Wang <gengliang@apache.org>
### What changes were proposed in this pull request? Add util methods to convert DS V2 Filter to V1 Filter. ### Why are the changes needed? Provide convenient methods to convert V2 to V1 Filters. These methods can be used by [`SupportsRuntimeFiltering`](https://github.com/apache/spark/pull/36918/files#diff-0d3268f351817ca948e75e7b6641e5cc67c4d773c3234920a7aa62faf11f6c8e) and later be used by `SupportsDelete` ### Does this PR introduce _any_ user-facing change? No. These are intended for internal use only ### How was this patch tested? new tests Closes apache#37332 from huaxingao/toV1. Authored-by: huaxingao <huaxin_gao@apple.com> Signed-off-by: huaxingao <huaxin_gao@apple.com>
…terval arithmetic overflow" This reverts commit 1b6f14f.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?