Hi all,
As we are getting closer to releasing Flink-1.3, I would like to open a
discussion
on how far back we provide backwards compatibility for.
The reason for opening the discussion is that i) for the users and for the
adoption of the project, it is good to have an explicitely stated policy
I think it would be a good to clarify what kind of
backwards-compatibilitiy we're talking about here. As in are we talking
about APIs or savepoints?
On 20.05.2017 19:09, Kostas Kloudas wrote:
Hi all,
As we are getting closer to releasing Flink-1.3, I would like to open a
discussion
on how fa
sunjincheng created FLINK-6649:
--
Summary: Improve Non-window group aggregate with configurable
`earlyFire`.
Key: FLINK-6649
URL: https://issues.apache.org/jira/browse/FLINK-6649
Project: Flink
Hi Chesnay,
I believe that for APIs we already have a pretty clear policy with the
annotations.
I was referring to savepoints and state related backwards compatibility.
> On May 20, 2017, at 7:20 PM, Chesnay Schepler wrote:
>
> I think it would be a good to clarify what kind of backwards-comp
sunjincheng created FLINK-6650:
--
Summary: Fix Non-windowed group-aggregate error when using
append-table mode.
Key: FLINK-6650
URL: https://issues.apache.org/jira/browse/FLINK-6650
Project: Flink
Ted Yu created FLINK-6651:
-
Summary: Clearing registeredStates map should be protected in
SharedStateRegistry#clear
Key: FLINK-6651
URL: https://issues.apache.org/jira/browse/FLINK-6651
Project: Flink
