-
Notifications
You must be signed in to change notification settings - Fork 13.9k
[FLINK-29749][client] Make 'flink info' command could support dynamic properties. #21165
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
Closed
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
Need to make sure the job manager runner is complete, because the test runner does not implement required methods to query job details.
…search7 connector
…ation Development > Table API & SQL" to Chinese. This closes apache#19401 Co-authored-by: Roc Marshal <flinker@126.com>
…cal sort is incorrect if adaptive batch scheduler is enabled (cherry picked from commit 456ceb2) This closes apache#19497
…binary/character string Revert behaviour of binary to string casts and vice versa, to not use hex enconding/decoding, but simple UTF-8 bytes transformation from a byte[] to a string and vice versa. (cherry picked from commit 4cdafff)
… `x'ab3234f0'` format Add an `isPrinting()` method to the `CastRule.Context` set to true used by `RowDataToStringConverterImpl` which defines a different casting behaviour for `BinaryToStringCastRule` when printing binary columns, so that we output columns of binary type as (for example): `x'ab03f98e'`, which can easily be copy pasted as a binary literal to another SQL query. (cherry picked from commit 75007f6) This closes apache#19516.
… name in DDL This closes apache#19490.
…Vulnerability. This closes apache#19479 Signed-off-by: David N Perkins <David.N.Perkins@ibm.com>
… compatible with legacy behavior This closes apache#19470.
…n Python DataStream API
… table source This closes apache#19551.
…rState may have not been updated when sechema changes
…eachableCoalesceArgumentsRule (cherry picked from commit 2e632af) This closes apache#19566
…ing of ExecutionGraphInfo finishes
…behavior This closes apache#19574
…Scheduler We change the signature of JobVertex#initializeOnMaster/finalizeOnMaster to pass a Context object. In this context we can pass the actual parallelism the vertex will be run with.
… FanOutRecordPublisher
Enum fields have naming restrictions in some languages.
…otation to JUnit5 annotation for disabling tests on Java 11
…l table with create-time mode This closes apache#20437.
…ointCommittableManagerImpl during deserialization. When we recover the `CheckpointCommittableManager` we were ignoring the subtaskId it is recovered on. This becomes a problem when a sink uses a post-commit topology because multiple committer operators might forward committable summaries coming from the same subtaskId. This ticket implements a fix to use the subtaskId already present in the CommittableCollectorSerializer when recreating CheckpointCommittableManagerImpl during recovery. Signed-off-by: Krzysztof Chmielewski <krzysiek.chmielewski@gmail.com>
…red (failed) readers This closes apache#21038
…bleWithLinages with the CommittableSummary Before this change during recovery for the CommitableCollector we initialized the SubtaskCommittableManager always with the initial checkpoint id (1) but the holding CheckpointCommittable with the checkpoint id in state. This could lead to that the emitted CommittableWithLinages update SubtaskCommittableManagers that they do not belong to cause "Unknown subtask for <id>" failures.
…utionConfig when creating serializer
…ng Table to DataStream This closes apache#21086.
…e test times out again.
Co-authored-by: Yufan Sheng <yufan@streamnative.io>
…on (apache#21100) This cherry-picks apache#21069. Co-authored-by: Yufan Sheng <yufan@streamnative.io>
… more than 1 committable. Recovery more than one Committable causes `IllegalStateException` and prevents cluster to start. When we recover the `CheckpointCommittableManager` we deserialize SubtaskCommittableManager instances from recovery state, and we put them into `Map<Integer, SubtaskCommittableManager<CommT>>`. The key of this map is subtaskId of the recovered manager. However, this will fail if we have to recover more than one committable. What was implemented as a fix is to call `SubtaskCommittableManager::merge` if we already deserialize manager for this subtaskId. Signed-off-by: Krzysztof Chmielewski <krzysiek.chmielewski@gmail.com>
… depdendency This closes apache#21110.
…tasks to avoid wasting resources This closes apache#21132.
…ythonOptionsTest This closes apache#21157.
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 is the purpose of the change
barkport for FLINK-29749
Brief change log
(for example:)
Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (yes / no)Documentation