Hi Godfrey,
I would like to share some problems based on my past experience.
1. It's not easy to push new features in the CALCITE community.
As @Martijn referred, https://issues.apache.org/jira/browse/CALCITE-4865 /
https://github.com/apache/calcite/pull/2606 is such an example.
I tried out many w
Gyula Fora created FLINK-27360:
--
Summary: Rename clusterId field of FlinkSessionJobSpec to
deploymentName
Key: FLINK-27360
URL: https://issues.apache.org/jira/browse/FLINK-27360
Project: Flink
Hi. Jiang.
Thanks for your feedback！
> Do the public interfaces of GatewayService refer to any service?
We will only expose one GatewayService implementation. We will put the
interface into the common package and the developer who wants to implement
a new endpoint can just rely on the interface
Jane Chan created FLINK-27361:
-
Summary: Introduce retry mechanism for SnapshotFinder
Key: FLINK-27361
URL: https://issues.apache.org/jira/browse/FLINK-27361
Project: Flink
Issue Type: Sub-task
Hi all,
I could share two cents here for how we maintain FRocksDB.
First of all, we also do not prefer to maintain a customized RocksDB version in
Flink, which brings additional overhead for Flink community:
1. RocksDB community switches to circleci for the CI tests after
RocksDB-6.x, whic
Aitozi created FLINK-27362:
--
Summary: Support restartNonce semantics in session job
Key: FLINK-27362
URL: https://issues.apache.org/jira/browse/FLINK-27362
Project: Flink
Issue Type: Sub-task
