Hello Ilya,
Thank you for your email. Yes, before we remove any integration we will
move them to another repository and release.
We are thinking we will start with Pub/Sub Streamer implementation and
continue to move other integration as mentioned in the following doc.
Hi Denis,
Yes, I see it now as I think more about it, I like option - 0. I am
thinking from a new member and a contributor perspective for Ignite
project, I would very much like my PR and proposal to be accepted within
Ignite community.
Regards,
Saikat
On Thu, Oct 24, 2019 at 1:56 PM Denis
Looping in dev list.
Folks, does anybody have any experience with Striim or ready to research?
https://www.striim.com/sources-and-targets/
It might be an option for change-data-capture scenarios from Ignite
clusters (with and without persistence) to other stores like RDBMS or
Cassandra.
-
Denis
Ignite user and dev community,
Next Tuesday I'll be in NY conducting in-memory computing essentials
session for one of the biggest meetup communities of the city [1]. Stop by
if you're around. Let's meet in person. Once the main track is over we can
stay and have a couple of beers/sodas
Exactly, Dmitry found the right word for the reason why option-0 might be
the best one - to avoid the Ignite community *split*. All those who will be
contributing to integrations and extensions need to be able to earn a
status of an Ignite committer and PMC members. Otherwise, I'm not sure if
Igniters,
Below is a list of proposed candidates. Let's give the candidates time
until Monday to either confirm or reject their candidacy. Those who confirm
will be sent for the vote. If we don't hear back from someone by that time,
then the silence will be treated as a rejection. Keep in mind
Igniters,
The Chair rotation discussion [1] triggered many questions such as why
would we rotate the Chair, what happens with the diversity, and overall
community growth. Let's use this thread to discuss the status of the
project and to highlight some areas of improvement in 2020. This will help
Hello!
My take on this: we want to offload some of integrations, but please commit
and release them to another project first, and only then we will decide to
remove them from our repository.
Please also make sure they are available with same artifact name and API.
If this has to be changed,
Hi Nikita,
1. As I can understand, this functionality is needed if a custom message is
needed to be processed only on the coordinator node. I'm not following for
what purposes it was implemented and I see the real usage only in tests.
As far as this functionality is not used in production code, I
Hi, Igniters.
The discovery custom message interface has two methods the use of
which is not clear to developers:
1. The stopProcess() method. Currently, it works only if the zookeeper
discovery configured. It doesn't work in TcpDiscoverySpi. I did not
find any usages of this method except
Alexey Zinoviev, Igniters, sorry for topic high-jacking / side reply, but I
have to stress one thing.
Both Committers and PMC groups are not a sort of clubs, it is just roles.
One can accept patches, another can reject a patch using veto and
suggest/vote for new committers.
There is nothing
Hi Vova,
Glad to hear from you. I hope that we will hear from you soon about
Hazelnite (Igncast?) independently whether you become Ignite PMC Chair
or not.
чт, 24 окт. 2019 г. в 11:49, Anton Vinogradov :
>
> Vova,
> +1 to your candidacy.
> Just say yes.
>
> As for me, huge thanks for the
Vova,
+1 to your candidacy.
Just say yes.
As for me, huge thanks for the proposal but being PMC Member currently
enough for me :)
On Thu, Oct 24, 2019 at 11:21 AM Dmitriy Pavlov wrote:
> Vova, I will vote for your candidacy as well. Your candidacy came for 2nd
> time (I've checked previous
Vova, I will vote for your candidacy as well. Your candidacy came for 2nd
time (I've checked previous thread).
This is a good sign that we should think about you serving as Chair.
чт, 24 окт. 2019 г. в 11:16, Vladimir Ozerov :
> HI Anton,
>
> Thanks for adding me to the list. Ignite community is
HI Anton,
Thanks for adding me to the list. Ignite community is very vibrant, it
would be a honor for me to resonate it even further. For example, I was
thinking about Ignite - Hazelcast integration (aka "Hazelnite") which could
have bring a lot of fresh technical discussions to the list.
But as
Wow, two opposite opinion about voting proccess in a drei minuten
I share the Dmitriy's thoughts about Apache Way and Denis and Nikolay, but
also support voting procedure if we will have more than 1 candidate.
Also will be a good point to find and share official or recommended rights
and area of
Some more candidates:
A. Gura
A. Vinogradov
чт, 24 окт. 2019 г. в 10:50, Anton Vinogradov :
>
> Agree with Alexey,
>
> Denis, could you please ask candidates privately whether they are ready to
> become a PMC Chair and start the vote with the confirmed list?
>
> On Thu, Oct 24, 2019 at 10:47 AM
Agree with Alexey,
Denis, could you please ask candidates privately whether they are ready to
become a PMC Chair and start the vote with the confirmed list?
On Thu, Oct 24, 2019 at 10:47 AM Alexey Zinoviev
wrote:
> Ha-ha, surely, I'm not a candidate to this place, but joining to the PMC
> club
Alexey, it's not a vote. Yes, it is a discussion, something in a free form.
You can suggest anyone from PMC who can serve this role, you can share any
of your thoughts.
I'm not aware of why to change Denis. I personally prefer to keep it as is,
since Denis Magda has proven he is open-minded and
Ha-ha, surely, I'm not a candidate to this place, but joining to the PMC
club will be a honor for me.
чт, 24 окт. 2019 г., 9:34 Anton Vinogradov :
> More candidates:
>
> - Alexey Zinoviev.
> He is not a PMC member, but it's definitely time to change this.
> BigData evangelist.
>
> - Ivan Rakov.
More candidates:
- Alexey Zinoviev.
He is not a PMC member, but it's definitely time to change this.
BigData evangelist.
- Ivan Rakov.
He is not a PMC member, but it's definitely time to change this.
Distributed systems evangelist and great lead.
- Denis Magda.
Keeping this stable is also the
I agree with option 0 now, we could start from that option, and later
migrate to the Bahir Community, if it is required.
чт, 24 окт. 2019 г., 9:04 Dmitriy Pavlov :
> Hah, IMHO, it is a story of how pushing others to place their contribution
> outside ASF could lead projects to split their
Currently, we discuss only candidates here, isn't it? This is not a vote?
Also we should ask candidates about their plans, isn't it?
Please, Denis, remind the procedure of voting, if we will have more than 1
candidate?
Ans yet one suggestion: maybe we will rotate every year, and it will be
easy
Hah, IMHO, it is a story of how pushing others to place their contribution
outside ASF could lead projects to split their communities.
I believe, the Ignite community is more open and flexible in that regard.
So Option-0. is also OK from my perspective.
чт, 24 окт. 2019 г. в 04:01, Saikat Maitra
Hi Igniters,
I would be happy to serve this role, but since my day job current projects
not related to Ignite, it may cause some delays in replies.
I would give my +1 to both candidates, but I'm concerned how keeping PMC
Chair inside the company initially donated code to ASF could move the
25 matches
Mail list logo
