yep, it seems you are right
we need 2 versions otherwise there will be clash between base artifact
from both v1 and v2
just faced this while preparations
On Tue, Apr 23, 2024 at 4:13 PM Sergey Nuyanzin wrote:
>
> thanks for your response, Danny
>
> yeah, I think we could have 2 releases: one for
I'm in a process of preparation of RC for OpenSearch connector
however it seems I need PMC help: need to create opensearch-2.0.0 on jira
since as it was proposed in another ML[1] to have 1.x for OpenSearch
v1 and 2.x for OpenSearch v2
would be great if someone from PMC could help here
[1] https:
Hi all,
If there are no more considerations, I'll open up a vote in the next couple
of days.
Best regards,
Martijn
On Wed, May 8, 2024 at 4:08 AM Hongshun Wang
wrote:
> Hi Martijn, Thanks for the proposal +1 from me.Some sinks still use
> sinkfunction; it's time to take a step forward.
>
> Be
Hi Xuannan,
Thanks for driving this FLIP!
I have a minor comment. Do we plan to remove StreamPipelineOptions in 2.0,
as it only contains deprecated options?
Regards,
Jeyhun
On Sat, May 11, 2024 at 4:40 AM Rui Fan <1996fan...@gmail.com> wrote:
> Thanks Xuannan for the update!
>
> LGTM, +1 for th
Thanks Martijn
I believe you missed my question,
Should this change take place in 1.20, what are the planned release steps
> for connectors that only offer a deprecated interface in this case (i.e.
> RabbitMQ, Cassandra, pusbub, Hbase)? Are we going to refrain from releases
> till the blockers are
Hello Danny,
Thanks for pushing this forward. I am available to assist with the CDC
connector[1].
[1] https://github.com/apache/flink-cdc
Best
Hongshun
On Sun, May 12, 2024 at 8:48 PM Sergey Nuyanzin wrote:
> I'm in a process of preparation of RC for OpenSearch connector
>
> however it seems
Hi Jeyhun,
Thanks for the comment!
Yes, we intended to remove the StreamPiplineOptions in 2.0. I updated
the FLIP to include the information.
Best regards,
Xuannan
On Sun, May 12, 2024 at 9:16 PM Jeyhun Karimov wrote:
>
> Hi Xuannan,
>
> Thanks for driving this FLIP!
> I have a minor comment.
Hi Kevin,
I think the question is valuable and It looks like this question can be
posted at the user email list to receive more feedback.
As for the question, I just want to share some observations:
1. When there are hundreds of data pipelines, it is nearly impossible to
make all of them work pro
>
> Note that for both recovery and checkpoints, there are no retring
> mechanisms. If any part of downloading or
> uploading fails, the job fails over, so actually using such interface
> extension would be out of scope of this FLIP. In
> that case, maybe if this could be extended in the future wi
+1 (non-binding)
- Validated checksum hash
- Verified signature
- Verified that no binaries exist in the source archive
- Build the source with Maven and jdk8
- Verified web PR
- Check that the jar is built by jdk8
- Check synchronizing schemas and data from mysql to starrocks following
the quicks
10 matches
Mail list logo