Hi Yazdan,
First of all, thank you for contributing to Flink!
As Chesnay said, many of the Flink committers try to review pull requests
in a timely manner.
However, everybody has to put time aside to review a PR.
Many committers are either working on features themselves or review PRs in
their fre
Deepak Sharma created FLINK-9563:
Summary: Migrate integration tests for CEP
Key: FLINK-9563
URL: https://issues.apache.org/jira/browse/FLINK-9563
Project: Flink
Issue Type: Sub-task
Alexandr Arkhipov created FLINK-9562:
Summary: Wrong wording in flink-optimizer module
Key: FLINK-9562
URL: https://issues.apache.org/jira/browse/FLINK-9562
Project: Flink
Issue Type: Bug
aitozi created FLINK-9561:
-
Summary: Lack of the api to set RocksDB Option by flink config
Key: FLINK-9561
URL: https://issues.apache.org/jira/browse/FLINK-9561
Project: Flink
Issue Type: Improvement
Hello,
These kind of lists are imo misguided as they setup false expectations.
They imply that "If I ping person X at time Y I will get a fast review",
which is just not true.
Thus, allow me to answer your questions:
“Who should I tag in my PR for code review?”
You shouldn't tag anyone in PR
Hi Stephan,
Thanks very much for your response! That gave me the confidence to continue to
work on the Elastic Filter. But even though we have implemented it(based on
1.3.2) and used it on production for a several months, If there's one commiter
is willing to guide me(since it's not a very tri
