cc user ML to get more attention, since the plugin will be used by Flink
application developers.
Best regards,
Jing
On Mon, May 22, 2023 at 3:32 PM Jing Ge wrote:
> Hi Emre,
>
> Thanks for clarifying it. Afaiac, it is a quite interesting proposal,
> especially for Flink job developers who are
Hi Emre,
Thanks for clarifying it. Afaiac, it is a quite interesting proposal,
especially for Flink job developers who are heavily using the Datastream
API. Publishing the plugin in your Github would be a feasible way for the
first move. As I mentioned previously, in order to help the community
Hi Jing,
The proposed plugin would be used by Flink application developers, when they
are writing their Flink job. It would trigger during compilation/packaging and
would look for known incompatibilities, bad practices, or bugs.
For instance one cause of frustration for our customers is
Hi Emre,
Thanks for your proposal. It looks very interesting! Please pay attention
that most connectors have been externalized. Will your proposed plug be
used for building Flink Connectors or Flink itself? Furthermore, it would
be great if you could elaborate features wrt best practices so that
Hello all,
Myself and 2 colleagues developed a Maven plugin (no support for Gradle or
other build tools yet) that we use internally to detect potential issues in
Flink apps at compilation/packaging stage:
* Known connector version incompatibilities – so far covering Kafka and
Kinesis
*
