[jira] [Commented] (FLINK-33355) can't reduce the parallelism from 'n' to '1' when recovering through a savepoint.

[ https://issues.apache.org/jira/browse/FLINK-33355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779340#comment-17779340 ] Yun Tang commented on FLINK-33355: -- [~edmond_j] could you please share the code to reproduce this

[jira] [Commented] (FLINK-33355) can't reduce the parallelism from 'n' to '1' when recovering through a savepoint.

[ https://issues.apache.org/jira/browse/FLINK-33355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779315#comment-17779315 ] Yun Tang commented on FLINK-33355: -- Changing the max-parallelism (instead of parallelism), would break

[jira] [Closed] (FLINK-33355) can't reduce the parallelism from 'n' to '1' when recovering through a savepoint.

[ https://issues.apache.org/jira/browse/FLINK-33355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang closed FLINK-33355. Resolution: Information Provided > can't reduce the parallelism from 'n' to '1' when recovering through a

[jira] [Commented] (FLINK-33341) Use available local state for rescaling

[ https://issues.apache.org/jira/browse/FLINK-33341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778665#comment-17778665 ] Yun Tang commented on FLINK-33341: -- Current FLIP-291 already supports local recovery with the adaptive

[jira] [Assigned] (FLINK-33230) Support Expanding ExecutionGraph to StreamGraph in Web UI

[ https://issues.apache.org/jira/browse/FLINK-33230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-33230: Assignee: Yu Chen > Support Expanding ExecutionGraph to StreamGraph in Web UI >

[jira] [Commented] (FLINK-32197) FLIP 246: Dynamic Kafka Source

[ https://issues.apache.org/jira/browse/FLINK-32197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767055#comment-17767055 ] Yun Tang commented on FLINK-32197: -- [~mason6345] Thanks for the information! I will also ask some guys

[jira] [Comment Edited] (FLINK-32197) FLIP 246: Dynamic Kafka Source

[ https://issues.apache.org/jira/browse/FLINK-32197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767055#comment-17767055 ] Yun Tang edited comment on FLINK-32197 at 9/20/23 8:59 AM: --- [~mason6345]

[jira] [Commented] (FLINK-32197) FLIP 246: Dynamic Kafka Source

[ https://issues.apache.org/jira/browse/FLINK-32197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766654#comment-17766654 ] Yun Tang commented on FLINK-32197: -- [~mason6345] I noticed that this this ticket has been created

[jira] [Commented] (FLINK-32783) Release Testing: Improve parallel download of RocksDB incremental state

[ https://issues.apache.org/jira/browse/FLINK-32783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762002#comment-17762002 ] Yun Tang commented on FLINK-32783: -- +1 for [~knaufk]'s advice, let's close this ticket [~renqs]. >

[jira] [Commented] (FLINK-32782) Release Testing: Disable WAL in RocksDBWriteBatchWrapper by default

[ https://issues.apache.org/jira/browse/FLINK-32782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762003#comment-17762003 ] Yun Tang commented on FLINK-32782: -- +1 for [~knaufk]'s advice, let's close this ticket [~renqs]. >

[jira] [Commented] (FLINK-32782) Release Testing: Disable WAL in RocksDBWriteBatchWrapper by default

[ https://issues.apache.org/jira/browse/FLINK-32782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761683#comment-17761683 ] Yun Tang commented on FLINK-32782: -- Same as I raised in FLINK-32783, why do we need to test this

[jira] [Commented] (FLINK-32783) Release Testing: Improve parallel download of RocksDB incremental state

[ https://issues.apache.org/jira/browse/FLINK-32783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761682#comment-17761682 ] Yun Tang commented on FLINK-32783: -- Why do we need to test this internal improvement manually? From my

[jira] [Commented] (FLINK-20886) Add the option to get a threaddump on checkpoint timeouts

[ https://issues.apache.org/jira/browse/FLINK-20886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761292#comment-17761292 ] Yun Tang commented on FLINK-20886: -- [~Zakelly] If the task cannot receive the checkpoint barrier due to

[jira] [Commented] (FLINK-14032) Make the cache size of RocksDBPriorityQueueSetFactory configurable

[ https://issues.apache.org/jira/browse/FLINK-14032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761288#comment-17761288 ] Yun Tang commented on FLINK-14032: -- [~lijinzhong] already assigned to you. > Make the cache size of

[jira] [Assigned] (FLINK-14032) Make the cache size of RocksDBPriorityQueueSetFactory configurable

[ https://issues.apache.org/jira/browse/FLINK-14032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-14032: Assignee: Jinzhong Li > Make the cache size of RocksDBPriorityQueueSetFactory configurable >

[jira] [Updated] (FLINK-14032) Make the cache size of RocksDBPriorityQueueSetFactory configurable

[ https://issues.apache.org/jira/browse/FLINK-14032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-14032: - Priority: Major (was: Minor) > Make the cache size of RocksDBPriorityQueueSetFactory configurable >

[jira] [Commented] (FLINK-32955) Support state compatibility between enabling TTL and disabling TTL

[ https://issues.apache.org/jira/browse/FLINK-32955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759840#comment-17759840 ] Yun Tang commented on FLINK-32955: -- +1 for this improvement, especially for setting the TTL on a job

[jira] [Updated] (FLINK-32955) Support state compatibility between enabling TTL and disabling TTL

[ https://issues.apache.org/jira/browse/FLINK-32955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-32955: - Priority: Major (was: Minor) > Support state compatibility between enabling TTL and disabling TTL >

[jira] [Resolved] (FLINK-32793) Release Testing: Verify FLINK-31535 - Extend watermark-related features for SQL

[ https://issues.apache.org/jira/browse/FLINK-32793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-32793. -- Resolution: Fixed > Release Testing: Verify FLINK-31535 - Extend watermark-related features for >

[jira] [Commented] (FLINK-13194) Add explicit clarification about thread-safety of state in document

[ https://issues.apache.org/jira/browse/FLINK-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756260#comment-17756260 ] Yun Tang commented on FLINK-13194: -- [~masteryhx] Thanks for the reminder, please help review my PR. >

[jira] [Assigned] (FLINK-13194) Add explicit clarification about thread-safety of state in document

[ https://issues.apache.org/jira/browse/FLINK-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-13194: Assignee: Yun Tang > Add explicit clarification about thread-safety of state in document >

[jira] [Commented] (FLINK-32833) Rocksdb CacheIndexAndFilterBlocks must be true when using shared memory

[ https://issues.apache.org/jira/browse/FLINK-32833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753907#comment-17753907 ] Yun Tang commented on FLINK-32833: -- FLINK-7289 is the original ticket to introduce these options. The

[jira] [Commented] (FLINK-32833) Rocksdb CacheIndexAndFilterBlocks must be true when using shared memory

[ https://issues.apache.org/jira/browse/FLINK-32833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753143#comment-17753143 ] Yun Tang commented on FLINK-32833: -- Hi [~mayuehappy], {{setCacheIndexAndFilterBlocks}} is necessary as

[jira] [Closed] (FLINK-32754) Using SplitEnumeratorContext.metricGroup() in restoreEnumerator causes NPE

[ https://issues.apache.org/jira/browse/FLINK-32754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang closed FLINK-32754. Resolution: Information Provided > Using SplitEnumeratorContext.metricGroup() in restoreEnumerator causes

[jira] [Assigned] (FLINK-25862) Refactor SharedStateRegistry to not limit StreamStateHandle to register/unregister

[ https://issues.apache.org/jira/browse/FLINK-25862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-25862: Assignee: Feifan Wang > Refactor SharedStateRegistry to not limit StreamStateHandle to >

[jira] [Commented] (FLINK-25862) Refactor SharedStateRegistry to not limit StreamStateHandle to register/unregister

[ https://issues.apache.org/jira/browse/FLINK-25862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751858#comment-17751858 ] Yun Tang commented on FLINK-25862: -- Already assigned to you, please go ahead. > Refactor

[jira] [Commented] (FLINK-32566) HeapBytesVector meets java.lang.NegativeArraySizeException

[ https://issues.apache.org/jira/browse/FLINK-32566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751546#comment-17751546 ] Yun Tang commented on FLINK-32566: -- The root cause, which is analysed by [~catyee], is that the size of

[jira] [Updated] (FLINK-31268) OperatorCoordinator.Context#metricGroup will return null when restore from a savepoint

[ https://issues.apache.org/jira/browse/FLINK-31268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-31268: - Fix Version/s: 1.18.0 > OperatorCoordinator.Context#metricGroup will return null when restore from a >

[jira] [Commented] (FLINK-31268) OperatorCoordinator.Context#metricGroup will return null when restore from a savepoint

[ https://issues.apache.org/jira/browse/FLINK-31268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751499#comment-17751499 ] Yun Tang commented on FLINK-31268: -- [~ruanhang1993] I think this is an actual blocker for releasing

[jira] [Updated] (FLINK-31268) OperatorCoordinator.Context#metricGroup will return null when restore from a savepoint

[ https://issues.apache.org/jira/browse/FLINK-31268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-31268: - Priority: Blocker (was: Major) > OperatorCoordinator.Context#metricGroup will return null when restore

[jira] [Commented] (FLINK-32754) Using SplitEnumeratorContext.metricGroup() in restoreEnumerator causes NPE

[ https://issues.apache.org/jira/browse/FLINK-32754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751098#comment-17751098 ] Yun Tang commented on FLINK-32754: -- I think this problem still existed, and [~ruanhang1993] could you

[jira] [Updated] (FLINK-32611) Redirect to Apache Paimon's link instead of legacy flink table store

[ https://issues.apache.org/jira/browse/FLINK-32611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-32611: - Component/s: Project Website > Redirect to Apache Paimon's link instead of legacy flink table store >

[jira] [Created] (FLINK-32611) Redirect to Apache Paimon's link instead of legacy flink table store

Yun Tang created FLINK-32611: Summary: Redirect to Apache Paimon's link instead of legacy flink table store Key: FLINK-32611 URL: https://issues.apache.org/jira/browse/FLINK-32611 Project: Flink

[jira] [Resolved] (FLINK-31535) Extend watermark-related features for SQL

[ https://issues.apache.org/jira/browse/FLINK-31535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-31535. -- Resolution: Fixed > Extend watermark-related features for SQL >

[jira] [Assigned] (FLINK-31819) Add document for using watermark advanced functions in sql

[ https://issues.apache.org/jira/browse/FLINK-31819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31819: Assignee: Yuan Kui > Add document for using watermark advanced functions in sql >

[jira] [Resolved] (FLINK-31539) Support to configure watermark alignment in sql layer

[ https://issues.apache.org/jira/browse/FLINK-31539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-31539. -- Resolution: Fixed merged in master: 8f64775e577bfe2dd11236d795d32dabd3b0a970 > Support to configure

[jira] [Resolved] (FLINK-31540) Support to set source idle-timeout options in sql layer

[ https://issues.apache.org/jira/browse/FLINK-31540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-31540. -- Resolution: Fixed merged in master: 2aa9af15b418fb4308d089dad37e6b483d8a772a > Support to set source

[jira] [Resolved] (FLINK-31819) Add document for using watermark advanced functions in sql

[ https://issues.apache.org/jira/browse/FLINK-31819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-31819. -- Resolution: Fixed merged in master: 5cacd1216b018f47939a5a6fa671e022a0836256 > Add document for

[jira] [Resolved] (FLINK-31536) Support to set watermark emit strategy in sql layer

[ https://issues.apache.org/jira/browse/FLINK-31536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-31536. -- Resolution: Fixed merged in master: a3471eab7595f5fca35c38d09b29a5689808f339 > Support to set

[jira] [Commented] (FLINK-31238) Use IngestDB to speed up Rocksdb rescaling recovery

[ https://issues.apache.org/jira/browse/FLINK-31238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743700#comment-17743700 ] Yun Tang commented on FLINK-31238: -- Since the feature freeze date for flink-1.18 is July 24th, and no

[jira] [Resolved] (FLINK-23484) Add benchmarks for the ChangelogStateBackend

[ https://issues.apache.org/jira/browse/FLINK-23484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-23484. -- Fix Version/s: 1.18.0 Resolution: Fixed > Add benchmarks for the ChangelogStateBackend >

[jira] [Commented] (FLINK-23484) Add benchmarks for the ChangelogStateBackend

[ https://issues.apache.org/jira/browse/FLINK-23484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743646#comment-17743646 ] Yun Tang commented on FLINK-23484: -- merged on flink-benchmarks side:

[jira] [Commented] (FLINK-23484) Add benchmarks for the ChangelogStateBackend

[ https://issues.apache.org/jira/browse/FLINK-23484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743364#comment-17743364 ] Yun Tang commented on FLINK-23484: -- merged on flink side:

[jira] [Commented] (FLINK-32566) HeapBytesVector meets java.lang.NegativeArraySizeException

[ https://issues.apache.org/jira/browse/FLINK-32566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741463#comment-17741463 ] Yun Tang commented on FLINK-32566: -- It seems that the {{HeapBytesVector}} would reserve for many times

[jira] [Updated] (FLINK-32566) HeapBytesVector meets java.lang.NegativeArraySizeException

[ https://issues.apache.org/jira/browse/FLINK-32566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-32566: - Affects Version/s: (was: 1.17.1) > HeapBytesVector meets java.lang.NegativeArraySizeException >

[jira] [Resolved] (FLINK-32186) Support subtask stack auto-search when redirecting from subtask backpressure tab

[ https://issues.apache.org/jira/browse/FLINK-32186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-32186. -- Fix Version/s: 1.18.0 1.17.2 Resolution: Fixed merged in master:

[jira] [Resolved] (FLINK-30751) Remove references to disableDataSync in RocksDB documentation

[ https://issues.apache.org/jira/browse/FLINK-30751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-30751. -- Fix Version/s: 1.18.0 1.16.3 1.17.2 Resolution: Fixed

[jira] [Commented] (FLINK-32204) ZooKeeperLeaderElectionTest.testZooKeeperReelectionWithReplacement fails with The ExecutorService is shut down already. No Callables can be executed on AZP

[ https://issues.apache.org/jira/browse/FLINK-32204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17728944#comment-17728944 ] Yun Tang commented on FLINK-32204: -- Another instance:

[jira] [Commented] (FLINK-31810) RocksDBException: Bad table magic number on checkpoint rescale

[ https://issues.apache.org/jira/browse/FLINK-31810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727905#comment-17727905 ] Yun Tang commented on FLINK-31810: -- [~david.artiga] One possible reason might be the duplicated stream,

[jira] [Assigned] (FLINK-32186) Support subtask stack auto-search when redirecting from subtask backpressure tab

[ https://issues.apache.org/jira/browse/FLINK-32186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-32186: Assignee: Yu Chen > Support subtask stack auto-search when redirecting from subtask backpressure

[jira] [Commented] (FLINK-32186) Support subtask stack auto-search when redirecting from subtask backpressure tab

[ https://issues.apache.org/jira/browse/FLINK-32186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726111#comment-17726111 ] Yun Tang commented on FLINK-32186: -- [~Yu Chen] Already assigned to you, please go ahead. > Support

[jira] [Updated] (FLINK-32186) Support subtask stack auto-search when redirecting from subtask backpressure tab

[ https://issues.apache.org/jira/browse/FLINK-32186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-32186: - Priority: Major (was: Not a Priority) > Support subtask stack auto-search when redirecting from

[jira] [Resolved] (FLINK-32145) Fix incorrect docker image links of specific versions in flink-web site

[ https://issues.apache.org/jira/browse/FLINK-32145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-32145. -- Resolution: Fixed > Fix incorrect docker image links of specific versions in flink-web site >

[jira] [Commented] (FLINK-32145) Fix incorrect docker image links of specific versions in flink-web site

[ https://issues.apache.org/jira/browse/FLINK-32145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724844#comment-17724844 ] Yun Tang commented on FLINK-32145: -- resolved in apache/flink-web:

[jira] [Created] (FLINK-32145) Fix incorrect docker image links of specific versions in flink-web site

Yun Tang created FLINK-32145: Summary: Fix incorrect docker image links of specific versions in flink-web site Key: FLINK-32145 URL: https://issues.apache.org/jira/browse/FLINK-32145 Project: Flink

[jira] [Assigned] (FLINK-32135) FRocksDB fix log file create failed caused by file name too long

[ https://issues.apache.org/jira/browse/FLINK-32135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-32135: Assignee: Feifan Wang > FRocksDB fix log file create failed caused by file name too long >

[jira] [Commented] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

[ https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724237#comment-17724237 ] Yun Tang commented on FLINK-31743: -- [~Feifan Wang] You can create another ticket to focus on the

[jira] [Commented] (FLINK-30559) May get wrong result for `if` expression if it's string data type

[ https://issues.apache.org/jira/browse/FLINK-30559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724179#comment-17724179 ] Yun Tang commented on FLINK-30559: -- [~luoyuxia] This bug has been reported by many guys, can we make it

[jira] [Commented] (FLINK-30018) NPE error in generated StreamExecCalc

[ https://issues.apache.org/jira/browse/FLINK-30018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724178#comment-17724178 ] Yun Tang commented on FLINK-30018: -- I think this problem is the same as FLINK-30559. > NPE error in

[jira] [Commented] (FLINK-31810) RocksDBException: Bad table magic number on checkpoint rescale

[ https://issues.apache.org/jira/browse/FLINK-31810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723056#comment-17723056 ] Yun Tang commented on FLINK-31810: -- To be honest, I doubt that this problem might be related with

[jira] [Commented] (FLINK-31810) RocksDBException: Bad table magic number on checkpoint rescale

[ https://issues.apache.org/jira/browse/FLINK-31810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722732#comment-17722732 ] Yun Tang commented on FLINK-31810: -- First of all, the RocksDB version between 1.14 and 1.15 does not

[jira] [Resolved] (FLINK-32096) Flink 1.17 doc points to non-existant branch in flink-training repo

[ https://issues.apache.org/jira/browse/FLINK-32096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-32096. -- Resolution: Fixed Already resolved, merged in master: 983035c1799ae985b6dbcac5320de4b8a866819f >

[jira] [Commented] (FLINK-32096) Flink 1.17 doc points to non-existant branch in flink-training repo

[ https://issues.apache.org/jira/browse/FLINK-32096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722676#comment-17722676 ] Yun Tang commented on FLINK-32096: -- [~samrat007] Thanks for the reporting, I will fix this problem. >

[jira] [Assigned] (FLINK-32096) Flink 1.17 doc points to non-existant branch in flink-training repo

[ https://issues.apache.org/jira/browse/FLINK-32096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-32096: Assignee: Yun Tang > Flink 1.17 doc points to non-existant branch in flink-training repo >

[jira] [Commented] (FLINK-31810) RocksDBException: Bad table magic number on checkpoint rescale

[ https://issues.apache.org/jira/browse/FLINK-31810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722656#comment-17722656 ] Yun Tang commented on FLINK-31810: -- [~david.artiga] what distributed-file-system did you use to store

[jira] [Commented] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

[ https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721759#comment-17721759 ] Yun Tang commented on FLINK-31743: -- merged in flink release-1.17:

[jira] [Commented] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

[ https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720472#comment-17720472 ] Yun Tang commented on FLINK-31743: -- merged in master: bdb0233eb83629c3bb1b1487057b22891c41c437 For

[jira] [Commented] (FLINK-32027) Batch jobs could hang at shuffle phase when max parallelism is really large

[ https://issues.apache.org/jira/browse/FLINK-32027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720378#comment-17720378 ] Yun Tang commented on FLINK-32027: -- [~Weijie Guo] [~zhuzh] Please take a look at this issue. > Batch

[jira] [Created] (FLINK-32027) Batch jobs could hang at shuffle phase when max parallelism is really large

Yun Tang created FLINK-32027: Summary: Batch jobs could hang at shuffle phase when max parallelism is really large Key: FLINK-32027 URL: https://issues.apache.org/jira/browse/FLINK-32027 Project: Flink

[jira] [Commented] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

[ https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715367#comment-17715367 ] Yun Tang commented on FLINK-31743: -- [~assassinj] Thanks for the information, already assigned to him.

[jira] [Assigned] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

[ https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31743: Assignee: Feifan Wang (was: jinghaihang) > Avoid relocating the RocksDB's log failure when

[jira] [Commented] (FLINK-31810) RocksDBException: Bad table magic number on checkpoint rescale

[ https://issues.apache.org/jira/browse/FLINK-31810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713512#comment-17713512 ] Yun Tang commented on FLINK-31810: -- First of all, we can certainly rescale from a checkpoint. Would

[jira] [Commented] (FLINK-31836) Upgrade Calcite version to 1.34.0

[ https://issues.apache.org/jira/browse/FLINK-31836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713507#comment-17713507 ] Yun Tang commented on FLINK-31836: -- I wonder will this upgrade break the compatibility of FlinkSQL

[jira] [Assigned] (FLINK-31238) Use IngestDB to speed up Rocksdb rescaling recovery

[ https://issues.apache.org/jira/browse/FLINK-31238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31238: Assignee: Yue Ma > Use IngestDB to speed up Rocksdb rescaling recovery >

[jira] [Commented] (FLINK-31795) Add Config to enable/disable savepoint cleanup

[ https://issues.apache.org/jira/browse/FLINK-31795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17712167#comment-17712167 ] Yun Tang commented on FLINK-31795: -- [~darenwkt] If users want to keep the full savepoint history, why

[jira] [Commented] (FLINK-27719) Create Apache Flink slack workspace

[ https://issues.apache.org/jira/browse/FLINK-27719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711648#comment-17711648 ] Yun Tang commented on FLINK-27719: -- I think this ticket shall be marked as resolved, right? [~xtsong]

[jira] [Assigned] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

[ https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31743: Assignee: jinghaihang > Avoid relocating the RocksDB's log failure when filename exceeds 255 >

[jira] [Commented] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

[ https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709363#comment-17709363 ] Yun Tang commented on FLINK-31743: -- [~assassinj] Thanks for creating this ticket, please go ahead. >

[jira] [Updated] (FLINK-31743) Avoid relocating the RocksDB's log failure when filename exceeds 255 characters

[ https://issues.apache.org/jira/browse/FLINK-31743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-31743: - Fix Version/s: 1.16.2 1.18.0 1.17.1 (was:

[jira] [Commented] (FLINK-24785) Relocate RocksDB's log under flink log directory by default

[ https://issues.apache.org/jira/browse/FLINK-24785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709234#comment-17709234 ] Yun Tang commented on FLINK-24785: -- [~assassinj] Which ticket did you create? I don't think we need to

[jira] [Commented] (FLINK-24785) Relocate RocksDB's log under flink log directory by default

[ https://issues.apache.org/jira/browse/FLINK-24785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17708258#comment-17708258 ] Yun Tang commented on FLINK-24785: -- [~assassinj] The "previous location" means the default location

[jira] [Commented] (FLINK-31706) The default source parallelism should be the same as execution's default parallelism under adaptive batch scheduler

[ https://issues.apache.org/jira/browse/FLINK-31706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707926#comment-17707926 ] Yun Tang commented on FLINK-31706: -- cc [~zhuzh] > The default source parallelism should be the same as

[jira] [Created] (FLINK-31706) The default source parallelism should be the same as execution's default parallelism under adaptive batch scheduler

Yun Tang created FLINK-31706: Summary: The default source parallelism should be the same as execution's default parallelism under adaptive batch scheduler Key: FLINK-31706 URL:

[jira] [Resolved] (FLINK-31683) Align the outdated Chinese filesystem connector docs

[ https://issues.apache.org/jira/browse/FLINK-31683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang resolved FLINK-31683. -- Resolution: Fixed merged. master: 370929c838fbac21cc51a225f3c690c1ee8931a8 release-1.17:

[jira] [Created] (FLINK-31683) Align the outdated Chinese filesystem connector docs

Yun Tang created FLINK-31683: Summary: Align the outdated Chinese filesystem connector docs Key: FLINK-31683 URL: https://issues.apache.org/jira/browse/FLINK-31683 Project: Flink Issue Type: Bug

[jira] [Commented] (FLINK-31679) [Flink][UI] Show data exchange type on web ui

[ https://issues.apache.org/jira/browse/FLINK-31679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707165#comment-17707165 ] Yun Tang commented on FLINK-31679: -- Do you think this ticket might be related to FLINK-25561 ? >

[jira] [Commented] (FLINK-31573) Nexmark performance drops in 1.17 compared to 1.13

[ https://issues.apache.org/jira/browse/FLINK-31573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707095#comment-17707095 ] Yun Tang commented on FLINK-31573: -- I think https://github.com/nexmark/nexmark/pull/43 could help

[jira] [Commented] (FLINK-24785) Relocate RocksDB's log under flink log directory by default

[ https://issues.apache.org/jira/browse/FLINK-24785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706709#comment-17706709 ] Yun Tang commented on FLINK-24785: -- [~assassinj] I think this is a valid problem. Will RocksDB store

[jira] [Assigned] (FLINK-31653) Using`if` statement for a string subtype of the row type may meet npe in code generated by codegen

[ https://issues.apache.org/jira/browse/FLINK-31653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31653: Assignee: Yuan Kui > Using`if` statement for a string subtype of the row type may meet npe in

[jira] [Updated] (FLINK-31653) Using`if` statement for a string subtype of the row type may meet npe in code generated by codegen

[ https://issues.apache.org/jira/browse/FLINK-31653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-31653: - Priority: Critical (was: Major) > Using`if` statement for a string subtype of the row type may meet

[jira] [Commented] (FLINK-31653) Using`if` statement for a string subtype of the row type may meet npe in code generated by codegen

[ https://issues.apache.org/jira/browse/FLINK-31653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706271#comment-17706271 ] Yun Tang commented on FLINK-31653: -- [~catyee] Thanks for creating this ticket. I think this is a valid

[jira] [Updated] (FLINK-31653) Using`if` statement for a string subtype of the row type may meet npe in code generated by codegen

[ https://issues.apache.org/jira/browse/FLINK-31653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang updated FLINK-31653: - Fix Version/s: 1.16.2 1.17.1 > Using`if` statement for a string subtype of the row

[jira] [Assigned] (FLINK-31536) Support to set watermark emit strategy in sql layer

[ https://issues.apache.org/jira/browse/FLINK-31536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31536: Assignee: Yuan Kui > Support to set watermark emit strategy in sql layer >

[jira] [Assigned] (FLINK-31539) Support to configure watermark alignment in sql layer

[ https://issues.apache.org/jira/browse/FLINK-31539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31539: Assignee: Yuan Kui > Support to configure watermark alignment in sql layer >

[jira] [Assigned] (FLINK-31540) Support to set source idle-timeout options in sql layer

[ https://issues.apache.org/jira/browse/FLINK-31540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31540: Assignee: Yuan Kui > Support to set source idle-timeout options in sql layer >

[jira] [Assigned] (FLINK-31535) Extend watermark-related features for SQL

[ https://issues.apache.org/jira/browse/FLINK-31535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31535: Assignee: yuankui > Extend watermark-related features for SQL >

[jira] [Assigned] (FLINK-31535) Extend watermark-related features for SQL

[ https://issues.apache.org/jira/browse/FLINK-31535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Tang reassigned FLINK-31535: Assignee: Yuan Kui (was: yuankui) > Extend watermark-related features for SQL >

[jira] [Commented] (FLINK-31238) Use IngestDB to speed up Rocksdb rescaling recovery

[ https://issues.apache.org/jira/browse/FLINK-31238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699160#comment-17699160 ] Yun Tang commented on FLINK-31238: -- [~mayuehappy] Thanks for the reply. Considering the efforts to

[jira] [Commented] (FLINK-31238) Use IngestDB to speed up Rocksdb rescaling recovery

[ https://issues.apache.org/jira/browse/FLINK-31238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697815#comment-17697815 ] Yun Tang commented on FLINK-31238: -- [~mayuehappy] Thanks for the great work! If my understanding is

[jira] [Commented] (FLINK-31366) Exception is thrown when s3a and s3p are used together

[ https://issues.apache.org/jira/browse/FLINK-31366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697783#comment-17697783 ] Yun Tang commented on FLINK-31366: -- I wonder will it break the backward compatibility with your current

<    1   2   3   4   5   6   7   8   9   10   >