Documentation update markdown #39
Closed
Conversation
This file contains 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
zhijiangW
pushed a commit
to zhijiangW/flink
that referenced
this pull request
Jul 23, 2019
This closes apache#39
uce
pushed a commit
to uce/flink
that referenced
this pull request
Aug 26, 2020
tzulitai
added a commit
to tzulitai/flink
that referenced
this pull request
Jan 15, 2021
The HttpFunction was relying on incorrect contracts promised by PersistedAppendingBuffer, causing it to endlessly resend 0-sized batch requests. This commit fixes that to rely on the revisited contracts. This closes apache#39.
lincoln-lil
pushed a commit
to lincoln-lil/flink
that referenced
this pull request
Oct 1, 2022
* [VVR-39543779][k8s] support respose for eviction label and disconnect tm * Merge branch &apache#39;master&apache#39; of gitlab.alibaba-inc.com:ververica/flink * Merge branch &apache#39;master&apache#39; of gitlab.alibaba-inc.com:ververica/flink * [VVR-39543779][k8s] Let k8s resourcemanager could respond to eviction labels Link: https://code.aone.alibaba-inc.com/ververica/flink/codereview/8048449 * [VVR-39543779][k8s] support respose for eviction label and disconnect tm * Merge branch 'master' of gitlab.alibaba-inc.com:ververica/flink * Merge branch 'master' of gitlab.alibaba-inc.com:ververica/flink * 'master' of gitlab.alibaba-inc.com:ververica/flink: (2114 commits) [VVR-39268526][table] Add table.exec.join.kv-separate to support statebackend kv-separate optimization. [VVR-40124095][state] Fix StateHandleForSavepointTest [VVR-40153420] Temporarily ignore JobMasterStopWithCheckpointITCase fix broken tests 【VVR-39683628][changelog] Support SortedMapState in changelog [VVR-40124095][table-planner] skip format validation exception caught before to fix test cases [VVR-40150090]更新基础镜像版本，支持中文 [hotfix][es] Ignore the IT cases based on test containers. [VVR-40124095][python] Fix the issue that RewriteWindowAggregateRule does't sup... [VVR-40124099][state] Fix SortedMapSerializerUpgradeTest and StateHandleForCheckpointTest [VVR-40006555][table-planner] Fix failed case in sql client and planner [VVR-40006555][table] Fix tools/ci/stage.sh [VVR-39680784][checkpoint] Leverage CLAIM restore mode [VVR-40006555][table] Fix merge error in ChangelogModeInferenceTest.testPropaga... [VVR-40006555][table] Remove flink-table-test-utils for stage tests [VVR-40055956][table-planner] Fix result of str_to_map when delimiters contain regex characters [VVR-39692635][table-planner] Remove useless code and correct the json ser/de logic [VVR-40006555][sqlserver] Fix failed tests in sqlserver hotfix: flink-runtime-web lint fix to pass ci-check hotfix: change npm registry to alibaba-inc ... * [VVR-39543779][k8s] Let k8s resourcemanager could respond to eviction labels
lincoln-lil
pushed a commit
to lincoln-lil/flink
that referenced
this pull request
Oct 1, 2022
…ourcePlanW... * When apply the resource plan, the applier get StreamNodes from the graph randomly. The origin resource plan modify the parallelism of the EvolvingDropUpdateBefore, which is in the middle of the plan. The test only check the exception when the source parallelism is different from the EvolvingDropUpdateBefore. It&apache#39;s possible that the applier get the downstream of the EvolvingDropUpdateBefore first and throw the unexpected exception message. Link: https://code.aone.alibaba-inc.com/ververica/flink/codereview/8144280 * [VVR-40137848][table] Fix unstable ResourcePlanApplyTest.testApplyResourcePlanWithIllegalParallelismForCTAS CTAS. * When apply the resource plan, the applier get StreamNodes from the graph randomly. The origin resource plan modify the parallelism of the EvolvingDropUpdateBefore, which is in the middle of the plan. The test only check the exception when the source parallelism is different from the EvolvingDropUpdateBefore. It's possible that the applier get the downstream of the EvolvingDropUpdateBefore first and throw the unexpected exception message.
lincoln-lil
pushed a commit
to lincoln-lil/flink
that referenced
this pull request
Oct 1, 2022
…ourcePlanW... * When apply the resource plan, the applier get StreamNodes from the graph randomly. The origin resource plan modify the parallelism of the EvolvingDropUpdateBefore, which is in the middle of the plan. The test only check the exception when the source parallelism is different from the EvolvingDropUpdateBefore. It&apache#39;s possible that the applier get the downstream of the EvolvingDropUpdateBefore first and throw the unexpected exception message. Link: https://code.aone.alibaba-inc.com/ververica/flink/codereview/8144280 * [VVR-40137848][table] Fix unstable ResourcePlanApplyTest.testApplyResourcePlanWithIllegalParallelismForCTAS CTAS. * When apply the resource plan, the applier get StreamNodes from the graph randomly. The origin resource plan modify the parallelism of the EvolvingDropUpdateBefore, which is in the middle of the plan. The test only check the exception when the source parallelism is different from the EvolvingDropUpdateBefore. It's possible that the applier get the downstream of the EvolvingDropUpdateBefore first and throw the unexpected exception message.
lincoln-lil
pushed a commit
to lincoln-lil/flink
that referenced
this pull request
Oct 1, 2022
…ed lookup join port shuo.cs&apache#39;s previous work of 35312428 to release-6.0, did some necessary change to the patch. Link: https://code.aone.alibaba-inc.com/ververica/flink/codereview/8288360
lincoln-lil
pushed a commit
to lincoln-lil/flink
that referenced
this pull request
Oct 1, 2022
…ints Currently, in LEGACY restore mode, shared state of incremental checkpoints can be discarded regardless of whether they were created by this job or not. This invalidates the checkpoint from which the job was restored. The bug was introduced in FLINK-24611. Before that, reference count was maintained for each shared state entry; "initial" checkpoints did not decrement this count, preventing their shared state from being discarded. This change makes SharedStateRegistry to: 1. Remember the max checkpiont ID encountered during recovery 2. Associate each shared state entry with a checkpoint ID that created it 3. Only discard the entry if its createdByCheckpointID > highestRetainCheckpointID (1) is called from: - CheckpointCoordinator.restoreSavepoint - to cover initial restore from a checkpoint - SharedStateFactory, when building checkpoint store - to cover the failover case (see DefaultExecutionGraphFactory.createAndRestoreExecutionGraph) Adjusting only the CheckpointCoordinator path isn&apache#39;t sufficient: - job recovers from an existing checkpoints, adds it to the store - a new checkpoint is created - with the default restore settings - a failure happens, job recovers from a newer checkpoint - when a newer checkpoint is subsumed, its (inherited) shared state might be deleted Link: https://code.aone.alibaba-inc.com/ververica/flink/codereview/8331302 * [FLINK-26985][runtime] Don't discard shared state of restored checkpoints Currently, in LEGACY restore mode, shared state of incremental checkpoints can be discarded regardless of whether they were created by this job or not. This invalidates the checkpoint from which the job was restored. The bug was introduced in FLINK-24611. Before that, reference count was maintained for each shared state entry; "initial" checkpoints did not decrement this count, preventing their shared state from being discarded. This change makes SharedStateRegistry to: 1. Remember the max checkpiont ID encountered during recovery 2. Associate each shared state entry with a checkpoint ID that created it 3. Only discard the entry if its createdByCheckpointID > highestRetainCheckpointID (1) is called from: - CheckpointCoordinator.restoreSavepoint - to cover initial restore from a checkpoint - SharedStateFactory, when building checkpoint store - to cover the failover case (see DefaultExecutionGraphFactory.createAndRestoreExecutionGraph) Adjusting only the CheckpointCoordinator path isn't sufficient: - job recovers from an existing checkpoints, adds it to the store - a new checkpoint is created - with the default restore settings - a failure happens, job recovers from a newer checkpoint - when a newer checkpoint is subsumed, its (inherited) shared state might be deleted
lincoln-lil
pushed a commit
to lincoln-lil/flink
that referenced
this pull request
Oct 1, 2022
…r nullability for result type of generated expressions * [FLINK-20765][table-planner] Fix ScalarOperatorGens doesn&apache#39;t set proper nullabil... * fix conflict Link: https://code.alibaba-inc.com/ververica/flink/codereview/9160147 * [FLINK-20765][table-planner] Fix ScalarOperatorGens doesn't set proper nullability for result type of generated expressions This closes apache#19851 * fix conflict
jnh5y
pushed a commit
to jnh5y/flink
that referenced
this pull request
Dec 18, 2023
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.
I transformed java_api_quickstart, run_example_quickstart and setup_quickstart to markdown and updated the links. I gave up on doing everything in markdown for some reasons:
a) using css in combination with markdown is a hassle (I used some image tags in the end)
b) tables with lists in them are not realizable with only markdown