thanks to Matthias, I read the previous email here, and I will express my
own views on some issues
@Matthias
My opinion is that the scheme of high-availability splitting of each
component should be retained. As mentioned in David, when we need to split
each component, we need to use each LeaderEl
Hi David,
Thanks for the explanation. Yes, I understand we are figuring out whether
it is OK to remove the existing interfaces. I definitely agree that we
should preserve the capability to eventually split components out to
separate processes.
I guess my question is, suppose we remove the interfa
Weijie Guo created FLINK-30359:
--
Summary: Encountered NoClassDefFoundError when using
flink-sql-connector-elasticsearch6
Key: FLINK-30359
URL: https://issues.apache.org/jira/browse/FLINK-30359
Project:
JUNRUILi created FLINK-30358:
Summary: Show the task manager id on the exception history page
Key: FLINK-30358
URL: https://issues.apache.org/jira/browse/FLINK-30358
Project: Flink
Issue Type: Im
+1 (non-binding)
1. Checked the artifacts (binaries, headers, versions)
2. Checked the signatures
3. Compiled code
4. Created docker images
5. Run some manual tests
6. Run the examples
Other than one small issue (which is a local one) everything works like
charm.
Thanks Matyas for taking care of
Hi Dong,
> Adding regarding the effort to add back the per-component election
capability: given that the implementation already follows per-process
election, and given that there will likely be a lot of extra
design/implementation/test effort needed to achieve the use-cases described
above, maybe
