Yun Gao created FLINK-26625:
---
Summary: KinesisFirehoseSinkITCase failed on azure due to Could
not find a valid Docker environment
Key: FLINK-26625
URL: https://issues.apache.org/jira/browse/FLINK-26625
Yun Gao created FLINK-26624:
---
Summary: Running HA (hashmap, async) end-to-end test failed on
azure due to unable to find master logs
Key: FLINK-26624
URL: https://issues.apache.org/jira/browse/FLINK-26624
Yun Gao created FLINK-26623:
---
Summary: BlobsCleanupITCase failed on azure
Key: FLINK-26623
URL: https://issues.apache.org/jira/browse/FLINK-26623
Project: Flink
Issue Type: Bug
Yun Gao created FLINK-26622:
---
Summary: Azure failed due to Connection timed out
Key: FLINK-26622
URL: https://issues.apache.org/jira/browse/FLINK-26622
Project: Flink
Issue Type: Bug
Hi there,
It is exciting to see the discussion of the release timeline! I agree that
the end of March is a proper date.
To make others easier get involved in this discussion, I think we may need
to provide a more straightforward feature list for the preview release. The
"Initial Feature Set" in
Yun Gao created FLINK-26621:
---
Summary: flink-tests failed on azure due to Error occurred in
starting fork
Key: FLINK-26621
URL: https://issues.apache.org/jira/browse/FLINK-26621
Project: Flink
@Konstantin: Yes I completely agree that for this release the API (CRD)
should be marked experimental!
I have opened a ticket to track this:
https://issues.apache.org/jira/browse/FLINK-26620
@Yang Wang : I think we still have plenty of time
to work on features like the session job before the
Gyula Fora created FLINK-26620:
--
Summary: Mark CRD classes experimental
Key: FLINK-26620
URL: https://issues.apache.org/jira/browse/FLINK-26620
Project: Flink
Issue Type: Sub-task
Hi everyone,
can we mark all the APIs as experimental/alpha so that it is clear that
these can be broken in future releases for now? I think this would be very
important given the early stage of the project. We want to be able to
address shortcomings without worrying too much about backwards
