Jingsong Lee created FLINK-17955:
Summary: BucketLifeCycleListener should just in Buckets
Key: FLINK-17955
URL: https://issues.apache.org/jira/browse/FLINK-17955
Project: Flink
Issue Type:
Tzu-Li (Gordon) Tai created FLINK-17954:
---
Summary: Do not multiplex remote function state into single
PersistedTable
Key: FLINK-17954
URL: https://issues.apache.org/jira/browse/FLINK-17954
Dian Fu created FLINK-17953:
---
Summary: OverWindow doesn't support to order by non-time attribute
in batch mode for Table API program
Key: FLINK-17953
URL: https://issues.apache.org/jira/browse/FLINK-17953
Dian Fu created FLINK-17952:
---
Summary: Improve the error message when old planner and batch mode
is used via EnvironmentSettings
Key: FLINK-17952
URL: https://issues.apache.org/jira/browse/FLINK-17952
Dian Fu created FLINK-17951:
---
Summary: Improve the console message about executing a PyFlink job
Key: FLINK-17951
URL: https://issues.apache.org/jira/browse/FLINK-17951
Project: Flink
Issue Type:
Stephan Ewen created FLINK-17950:
Summary: Broken Scala env.countinuousSource method
Key: FLINK-17950
URL: https://issues.apache.org/jira/browse/FLINK-17950
Project: Flink
Issue Type: Bug
> A use case for this might be when you want to rollback a framework
upgrade (after some time) due to e.g. a performance
or stability issue.
Downgrade (that Konstantin called out) is an important and realistic
scenario. It will be great to support backward compatibility for savepoint
or at least
Robert Metzger created FLINK-17949:
--
Summary:
KafkaShuffleITCase.testSerDeIngestionTime:156->testRecordSerDe:388
expected:<310> but was:<0>
Key: FLINK-17949
URL:
In the beginning, I have somehow similar concerns as Piotr mentioned below.
After some offline discussions, also as explained by Stephan and Becket here, I
am +1 to backport it to release-1.11.
Best,
Zhijiang
--
From:Piotr
Shengkai Fang created FLINK-17948:
-
Summary: Strange precision performance of Timestamp and Decimal
Key: FLINK-17948
URL: https://issues.apache.org/jira/browse/FLINK-17948
Project: Flink
If we change the meaning of the priority levels, then I would suggest to
have a dedicated discussion for it. This would also be more visible than
compared to being hidden in some lengthy discussion thread. I think the
proposed definitions of priority levels differ slightly from how the
community
Till Rohrmann created FLINK-17947:
-
Summary: Retry REST requests if RpcEndpoint died before responding
to request
Key: FLINK-17947
URL: https://issues.apache.org/jira/browse/FLINK-17947
Project:
Dian Fu created FLINK-17946:
---
Summary: The config option "pipeline.jars" doesn't work if the job
was executed via TableEnvironment.execute_sql and StatementSet.execute
Key: FLINK-17946
URL:
Hi,
1. I'm okay with updating the definition of the priorities for the reason
you've mentioned.
2. "Affects version"
The reason why like to mark affects version on unreleased versions is to
clearly indicate which branch is affected by a bug. Given the current Flink
release status, if there's a
Robert Metzger created FLINK-17945:
--
Summary: Improve error reporting of Python CI tests
Key: FLINK-17945
URL: https://issues.apache.org/jira/browse/FLINK-17945
Project: Flink
Issue Type:
Jeff Zhang created FLINK-17944:
--
Summary: Wrong output in sql client's table mode
Key: FLINK-17944
URL: https://issues.apache.org/jira/browse/FLINK-17944
Project: Flink
Issue Type: Improvement
Caizhi Weng created FLINK-17943:
---
Summary: HiveFunctionWrapper#getUDFClass should use
Thread.currentThread().getContextClassLoader()
Key: FLINK-17943
URL: https://issues.apache.org/jira/browse/FLINK-17943
Benchao Li created FLINK-17942:
--
Summary: Count distinct could not clean state in WindowOperator
Key: FLINK-17942
URL: https://issues.apache.org/jira/browse/FLINK-17942
Project: Flink
Issue
Rui Li created FLINK-17941:
--
Summary: Switching database doesn't work from SQL CLI
Key: FLINK-17941
URL: https://issues.apache.org/jira/browse/FLINK-17941
Project: Flink
Issue Type: Bug
Shengkai Fang created FLINK-17940:
-
Summary: It will throw NullPointerException when write data with
Avro format using new property key in SQL-Client
Key: FLINK-17940
URL:
Hi,
It might have been implicit choice, but so far we were not supporting the
scenario that you are asking for. It has never been tested and we have lot’s of
state migration code sprinkled among our code base (for example upgrading state
fields of the operators like [1]), that only supports
Hi everyone,
I recently stumbled across the fact that Savepoints created with Flink 1.11
can not be read by Flink 1.10. A use case for this might be when you want
to rollback a framework upgrade (after some time) due to e.g. a performance
or stability issue.
>From the documentation [1] it seems
Hi,
As we discussed this offline a bit, initially I was sceptical to merge it,
as:
- even it’s an isolated change, it can destabilise the builds and prolong
release testing period
- is distracting from solving release blockers etc
However all in all I’m +0.5 to merge it because of this argument:
Usually we should avoid checking in patches other than bug fix after
feature freeze. However, in this particular case, the code base is sort of
in an incomplete state - an exposed known-to-change feature - due to
missing this patch. Fixing forward seems the best option. Besides that,
FLIP-27 has
Hi,
Sorry for a bit late response. I have two concerns:
1. Priority
I would propose to stretch priorities that we are using to differentiate
between things that must be fixed for given release:
BLOCKER - drop anything you are doing, this issue must be fixed right now
CRITICAL - release can
Jark Wu created FLINK-17939:
---
Summary: Translate "Python Table API Installation" page into
Chinese
Key: FLINK-17939
URL: https://issues.apache.org/jira/browse/FLINK-17939
Project: Flink
Issue
Till Rohrmann created FLINK-17938:
-
Summary: Cannot run mvn clean verify flink-yarn-tests
Key: FLINK-17938
URL: https://issues.apache.org/jira/browse/FLINK-17938
Project: Flink
Issue Type:
Hi all!
I want to discuss merging this PR to the 1.11 release branch:
https://github.com/apache/flink/pull/12306
It contains the new FLIP-126 Watermarks, and per-partition watermarking to
the FLIP-27 sources. In that sense it is partially a new feature after the
feature freeze. Hence this
Rui Li created FLINK-17937:
--
Summary: Change some hive connector tests to IT cases
Key: FLINK-17937
URL: https://issues.apache.org/jira/browse/FLINK-17937
Project: Flink
Issue Type: Test
Timo Walther created FLINK-17936:
Summary: Implement type inference for AS
Key: FLINK-17936
URL: https://issues.apache.org/jira/browse/FLINK-17936
Project: Flink
Issue Type: Sub-task
30 matches
Mail list logo
