Re: [VOTE] Release Apache Ignite 3.0.0-alpha3 RC1

[Valentin Kulichenko]

Pavel,

You've mentioned in the ticket that "Note that NuGet, unfortunately, has no
concept of "staging" (unlike Maven). A package with the given version can
be published only once, and it can't be undone. We can only publish the
packages after the successful vote."

With that, will you be okay if we proceed with the release, and upload the
NuGet package after the vote is accepted?

We can then have a separate discussion on the overall packaging approach.

-Val

On Wed, Oct 13, 2021 at 9:57 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Pavel,
>
> That's actually by design. The current packaging model assumes that we use
> Maven/NuGet to deliver binaries - both for servers side and client side. In
> case you have any objections to the overall approach, we surely can have a
> discussion, but I propose we do this separately after the release.
>
> However, it's great that you pointed this out as we indeed don't have the
> .NET package deployed. I've created a blocker ticket for this:
> https://issues.apache.org/jira/browse/IGNITE-15741
>
> Java client is deployed to Maven staging and examples are
> fully-functional, so we are good on that part.
>
> -Val
>
> On Wed, Oct 13, 2021 at 9:11 AM Pavel Tupitsyn 
> wrote:
>
>> To clarify, Java thin client has the following features:
>> - Table API
>> - Key-value API
>> - JDBC driver
>>
>> .NET thin client:
>> - Table API
>>
>> I think all of this should be included in the binary release.
>>
>> On Wed, Oct 13, 2021 at 10:10 AM Pavel Tupitsyn 
>> wrote:
>>
>> > -1 (binding)
>> >
>> > Java thin client and .NET thin client are missing from the binary
>> package.
>> >
>> >
>> > On Wed, Oct 13, 2021 at 3:03 AM Saikat Maitra 
>> > wrote:
>> >
>> >> +1 (binding)
>> >>
>> >> Regards
>> >> Saikat
>> >>
>> >> On Tue, Oct 12, 2021 at 5:03 PM Denis Magda  wrote:
>> >>
>> >> > +1 (binding)
>> >> >
>> >> > -
>> >> > Denis
>> >> >
>> >> >
>> >> > On Tue, Oct 12, 2021 at 6:01 PM Valentin Kulichenko <
>> >> > valentin.kuliche...@gmail.com> wrote:
>> >> >
>> >> > > Dear Community,
>> >> > >
>> >> > > Ignite 3 development is moving forward. In the last several months
>> >> we've
>> >> > > added the following features:
>> >> > >
>> >> > >- New SQL engine based on Apache Calcite + JDBC driver.
>> >> > >- Persistence implementation based on RocksDB.
>> >> > >- New binary client protocol with an implementation in Java.
>> >> > >- Data rebalancing.
>> >> > >
>> >> > > This is a significant milestone, so I think it will be valuable to
>> >> share
>> >> > > the current state with the broader community.
>> >> > >
>> >> > > I propose to release 3.0.0 Alpha3 with the features listed above.
>> >> > >
>> >> > > Please vote.
>> >> > >
>> >> > > ---
>> >> > >
>> >> > > Release candidate:
>> >> > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha3-rc1/
>> >> > > Maven staging:
>> >> > >
>> >>
>> https://repository.apache.org/content/repositories/orgapacheignite-1532
>> >> > > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha3-rc1
>> >> > >
>> >> > > +1 - accept Apache Ignite 3.0.0-alpha3 RC1
>> >> > >  0 - don't care either way
>> >> > > -1 - DO NOT accept Apache Ignite 3.0.0-alpha3 RC1 (explain why)
>> >> > >
>> >> > > Voting guidelines: https://www.apache.org/foundation/voting.html
>> >> > > How to verify the release:
>> >> https://www.apache.org/info/verification.html
>> >> > >
>> >> > > The vote will be open for 72 hours and will close on October 15th
>> at
>> >> 10pm
>> >> > > UTC:
>> >> > >
>> >> > >
>> >> >
>> >>
>> https://www.timeanddate.com/counters/fullscreen.html?mode=a&iso=20211015T15&year=2021&month=10&day=15&hour=15&min=0&sec=0&p0=224
>> >> > >
>> >> > > -Val
>> >> > >
>> >> >
>> >>
>> >
>>
>

Re: [VOTE] Release Apache Ignite 3.0.0-alpha3 RC1

[Valentin Kulichenko]

Hi Pavel,

That's actually by design. The current packaging model assumes that we use
Maven/NuGet to deliver binaries - both for servers side and client side. In
case you have any objections to the overall approach, we surely can have a
discussion, but I propose we do this separately after the release.

However, it's great that you pointed this out as we indeed don't have the
.NET package deployed. I've created a blocker ticket for this:
https://issues.apache.org/jira/browse/IGNITE-15741

Java client is deployed to Maven staging and examples are fully-functional,
so we are good on that part.

-Val

On Wed, Oct 13, 2021 at 9:11 AM Pavel Tupitsyn  wrote:

> To clarify, Java thin client has the following features:
> - Table API
> - Key-value API
> - JDBC driver
>
> .NET thin client:
> - Table API
>
> I think all of this should be included in the binary release.
>
> On Wed, Oct 13, 2021 at 10:10 AM Pavel Tupitsyn 
> wrote:
>
> > -1 (binding)
> >
> > Java thin client and .NET thin client are missing from the binary
> package.
> >
> >
> > On Wed, Oct 13, 2021 at 3:03 AM Saikat Maitra 
> > wrote:
> >
> >> +1 (binding)
> >>
> >> Regards
> >> Saikat
> >>
> >> On Tue, Oct 12, 2021 at 5:03 PM Denis Magda  wrote:
> >>
> >> > +1 (binding)
> >> >
> >> > -
> >> > Denis
> >> >
> >> >
> >> > On Tue, Oct 12, 2021 at 6:01 PM Valentin Kulichenko <
> >> > valentin.kuliche...@gmail.com> wrote:
> >> >
> >> > > Dear Community,
> >> > >
> >> > > Ignite 3 development is moving forward. In the last several months
> >> we've
> >> > > added the following features:
> >> > >
> >> > >- New SQL engine based on Apache Calcite + JDBC driver.
> >> > >- Persistence implementation based on RocksDB.
> >> > >- New binary client protocol with an implementation in Java.
> >> > >- Data rebalancing.
> >> > >
> >> > > This is a significant milestone, so I think it will be valuable to
> >> share
> >> > > the current state with the broader community.
> >> > >
> >> > > I propose to release 3.0.0 Alpha3 with the features listed above.
> >> > >
> >> > > Please vote.
> >> > >
> >> > > ---
> >> > >
> >> > > Release candidate:
> >> > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha3-rc1/
> >> > > Maven staging:
> >> > >
> >> https://repository.apache.org/content/repositories/orgapacheignite-1532
> >> > > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha3-rc1
> >> > >
> >> > > +1 - accept Apache Ignite 3.0.0-alpha3 RC1
> >> > >  0 - don't care either way
> >> > > -1 - DO NOT accept Apache Ignite 3.0.0-alpha3 RC1 (explain why)
> >> > >
> >> > > Voting guidelines: https://www.apache.org/foundation/voting.html
> >> > > How to verify the release:
> >> https://www.apache.org/info/verification.html
> >> > >
> >> > > The vote will be open for 72 hours and will close on October 15th at
> >> 10pm
> >> > > UTC:
> >> > >
> >> > >
> >> >
> >>
> https://www.timeanddate.com/counters/fullscreen.html?mode=a&iso=20211015T15&year=2021&month=10&day=15&hour=15&min=0&sec=0&p0=224
> >> > >
> >> > > -Val
> >> > >
> >> >
> >>
> >
>

Re: [VOTE] Release Apache Ignite 3.0.0-alpha3 RC1

[Pavel Tupitsyn]

To clarify, Java thin client has the following features:
- Table API
- Key-value API
- JDBC driver

.NET thin client:
- Table API

I think all of this should be included in the binary release.

On Wed, Oct 13, 2021 at 10:10 AM Pavel Tupitsyn 
wrote:

> -1 (binding)
>
> Java thin client and .NET thin client are missing from the binary package.
>
>
> On Wed, Oct 13, 2021 at 3:03 AM Saikat Maitra 
> wrote:
>
>> +1 (binding)
>>
>> Regards
>> Saikat
>>
>> On Tue, Oct 12, 2021 at 5:03 PM Denis Magda  wrote:
>>
>> > +1 (binding)
>> >
>> > -
>> > Denis
>> >
>> >
>> > On Tue, Oct 12, 2021 at 6:01 PM Valentin Kulichenko <
>> > valentin.kuliche...@gmail.com> wrote:
>> >
>> > > Dear Community,
>> > >
>> > > Ignite 3 development is moving forward. In the last several months
>> we've
>> > > added the following features:
>> > >
>> > >- New SQL engine based on Apache Calcite + JDBC driver.
>> > >- Persistence implementation based on RocksDB.
>> > >- New binary client protocol with an implementation in Java.
>> > >- Data rebalancing.
>> > >
>> > > This is a significant milestone, so I think it will be valuable to
>> share
>> > > the current state with the broader community.
>> > >
>> > > I propose to release 3.0.0 Alpha3 with the features listed above.
>> > >
>> > > Please vote.
>> > >
>> > > ---
>> > >
>> > > Release candidate:
>> > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha3-rc1/
>> > > Maven staging:
>> > >
>> https://repository.apache.org/content/repositories/orgapacheignite-1532
>> > > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha3-rc1
>> > >
>> > > +1 - accept Apache Ignite 3.0.0-alpha3 RC1
>> > >  0 - don't care either way
>> > > -1 - DO NOT accept Apache Ignite 3.0.0-alpha3 RC1 (explain why)
>> > >
>> > > Voting guidelines: https://www.apache.org/foundation/voting.html
>> > > How to verify the release:
>> https://www.apache.org/info/verification.html
>> > >
>> > > The vote will be open for 72 hours and will close on October 15th at
>> 10pm
>> > > UTC:
>> > >
>> > >
>> >
>> https://www.timeanddate.com/counters/fullscreen.html?mode=a&iso=20211015T15&year=2021&month=10&day=15&hour=15&min=0&sec=0&p0=224
>> > >
>> > > -Val
>> > >
>> >
>>
>

Re: Updating Javascript npm Package

[Igor Sapego]

Kevin,

Basically, to change this we need people who would actively drive
development of the client and be active community members.

Best Regards,
Igor


On Mon, Sep 27, 2021 at 6:02 PM Ivan Daschinsky  wrote:

> Hi! I can share my experience how to drive this activity. Personally, I've
> driven four recent releases of python thin client (pyignite). First of all,
> you should start a discussion, this thread is a good place to start.
> Secondly, you should prepare release branch (with help of commiters),
> create realease notes, etc. Secondly, PMC member should prepare rc
> artifact, sign with signature, theb publish it in apache svn for voting.
> After successful voting, release artifact can be published to npmjs.
>
> Let's start this activity!
>
> пн, 27 сент. 2021 г., 18:52 Kevin Corbett :
>
>> Hello Igniters!
>>
>> I’ve been helping with the Ignite social media channels for the last
>> month now. Lately I’ve been trying to increase awareness of our Javascript
>> capabilities, namely the thin client. Someone on our Twitter page had
>> mentioned the npm package hasn’t been updated in 3 years (!)
>>
>> I see our Github for the thin client was last updated in January this
>> year. What can we do to get this updated?
>> https://www.npmjs.com/package/apache-ignite-client <
>> https://www.npmjs.com/package/apache-ignite-client>
>>
>> Also, I saw there was an attempt to add Apache Ignite support to TypeORM
>> but there were many issues with the client.
>> https://github.com/typeorm/typeorm/pull/7012
>
>

Re: Move Azure, AWS, GCE to the ignite-extensions

[Stephen Darlington]

Okay, I phrased that badly. I mean an extra platform-specific ZIP file that I 
used to augment the generic Ignite ZIP file.

So, to run on Azure I’d download ignite.zip + azure.zip.

Extending ignite.sh would also be great, kind of like what’s happening with 
Ignite 3 as far as I can tell.

What I’m advocating is not needing to use Maven just to run Ignite on Azure, 
AWS, etc.

> On 13 Oct 2021, at 14:35, Petr Ivanov  wrote:
> 
> Our self-contained zip file currently is over 400Mb and continues to grow.
> Even considering that internet speeds has grown too, it is nonsense to force 
> user to download such an archive where 90% are useless for most cases.
> 
> Also we can:
> — pack all extensions in single binary with latests releases (and update 
> after each extension release) or even one by one
> — extend ignite.sh to download remote libs when extension is activated via 
> command line
> 
> 
> Antoine de Saint-Exupéry once said that 'perfection is achieved, not when 
> there is nothing more to add, but when there is nothing left to take away'.
> We are not obliged to make Apache Ignite ideal, but we certainly can move 
> that way — I am sure the result will exceed expectations.
> 
> 
> 
>> On 13 Oct 2021, at 16:02, Stephen Darlington 
>>  wrote:
>> 
>> Having extensions in Maven Central makes perfect sense for tools that need 
>> to be built and integrated with other code, Spring integrations for example.
>> 
>> That’s not the case for extensions that are required just to run Ignite. A 
>> self-contained zip file for each platform would work.
>> 
>>> On 13 Oct 2021, at 13:41, Maxim Muzafarov  wrote:
>>> 
>>> Nikolay,
>>> 
>>> All extensions will be available at the maven central for download.
>>> 
>>> Previously extensions have a dependent version on the ignite core, so
>>> each time the Ignite was released it made sense to include all the
>>> extensions into the uber-zip file. Each extension has its own release
>>> version now, so an extension can be upgraded and used independently,
>>> what is the reason include it in the single uber-zip file? Probably it
>>> would be better to provide a self-contained zip file for each cloud
>>> platform.
>>> 
>>> If I've missed your issue, so can you clarify the problem in more detail?
>>> 
>>> On Wed, 13 Oct 2021 at 14:37, Nikolay Izhikov  wrote:
 
 Maxim.
 
> Currently, they are copied from the optional
> directory of the ignite binary package but would be copied from an
> appropriate ignite extension binary package.
 
 But how, the user will download this binary package?
 Right now, all the user need is Ignite distributive.
 
 
> 13 окт. 2021 г., в 14:32, Maxim Muzafarov  написал(а):
> 
> Stephen,
> 
> I guess the required classes of IP-finders should be in the classpath
> (libs directory). Currently, they are copied from the optional
> directory of the ignite binary package but would be copied from an
> appropriate ignite extension binary package. Probably I'm missing
> something but almost nothing changes in that process from my point of
> view. The documentation pages will be updated prior to the release.
> 
> On Wed, 13 Oct 2021 at 13:44, Stephen Darlington
>  wrote:
>> 
>> I understand the motivation from a development point of view, but how 
>> will this work for end users? Currently, the documentation talks about 
>> extensions only in terms of importing maven dependencies (download.cgi 
>> ). If I’m trying to 
>> start a cluster on Azure, how does that work? Do I need to build my own 
>> server?
>> 
>> Regards,
>> Stephen
>> 
>>> On 13 Oct 2021, at 11:35, Nikita Amelchev  wrote:
>>> 
>>> +1 to migrate and include to the Ignite 2.12 scope
>>> 
>>> пн, 20 сент. 2021 г. в 17:09, Denis Magda :
 
 Perfect, thanks, Maxim!
 
 -
 Denis
 
 
 On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  
 wrote:
 
> Folks,
> 
> 
> I've created an issue [1] to move all cloud-based IP-finders to the
> ignite-extensions. The motivation is the same as with migration of
> Spring Data integration - to remove integration dependency of the
> release cycle on Ignite releases.
> 
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-15541
> 
>>> 
>>> 
>>> 
>>> --
>>> Best wishes,
>>> Amelchev Nikita
>> 
>> 
 
>> 
>> 
> 

Re: Move Azure, AWS, GCE to the ignite-extensions

[Petr Ivanov]

Our self-contained zip file currently is over 400Mb and continues to grow.
Even considering that internet speeds has grown too, it is nonsense to force 
user to download such an archive where 90% are useless for most cases.

Also we can:
 — pack all extensions in single binary with latests releases (and update after 
each extension release) or even one by one
 — extend ignite.sh to download remote libs when extension is activated via 
command line


Antoine de Saint-Exupéry once said that 'perfection is achieved, not when there 
is nothing more to add, but when there is nothing left to take away'.
We are not obliged to make Apache Ignite ideal, but we certainly can move that 
way — I am sure the result will exceed expectations.



> On 13 Oct 2021, at 16:02, Stephen Darlington 
>  wrote:
> 
> Having extensions in Maven Central makes perfect sense for tools that need to 
> be built and integrated with other code, Spring integrations for example.
> 
> That’s not the case for extensions that are required just to run Ignite. A 
> self-contained zip file for each platform would work.
> 
>> On 13 Oct 2021, at 13:41, Maxim Muzafarov  wrote:
>> 
>> Nikolay,
>> 
>> All extensions will be available at the maven central for download.
>> 
>> Previously extensions have a dependent version on the ignite core, so
>> each time the Ignite was released it made sense to include all the
>> extensions into the uber-zip file. Each extension has its own release
>> version now, so an extension can be upgraded and used independently,
>> what is the reason include it in the single uber-zip file? Probably it
>> would be better to provide a self-contained zip file for each cloud
>> platform.
>> 
>> If I've missed your issue, so can you clarify the problem in more detail?
>> 
>> On Wed, 13 Oct 2021 at 14:37, Nikolay Izhikov  wrote:
>>> 
>>> Maxim.
>>> 
 Currently, they are copied from the optional
 directory of the ignite binary package but would be copied from an
 appropriate ignite extension binary package.
>>> 
>>> But how, the user will download this binary package?
>>> Right now, all the user need is Ignite distributive.
>>> 
>>> 
 13 окт. 2021 г., в 14:32, Maxim Muzafarov  написал(а):
 
 Stephen,
 
 I guess the required classes of IP-finders should be in the classpath
 (libs directory). Currently, they are copied from the optional
 directory of the ignite binary package but would be copied from an
 appropriate ignite extension binary package. Probably I'm missing
 something but almost nothing changes in that process from my point of
 view. The documentation pages will be updated prior to the release.
 
 On Wed, 13 Oct 2021 at 13:44, Stephen Darlington
  wrote:
> 
> I understand the motivation from a development point of view, but how 
> will this work for end users? Currently, the documentation talks about 
> extensions only in terms of importing maven dependencies (download.cgi 
> ). If I’m trying to 
> start a cluster on Azure, how does that work? Do I need to build my own 
> server?
> 
> Regards,
> Stephen
> 
>> On 13 Oct 2021, at 11:35, Nikita Amelchev  wrote:
>> 
>> +1 to migrate and include to the Ignite 2.12 scope
>> 
>> пн, 20 сент. 2021 г. в 17:09, Denis Magda :
>>> 
>>> Perfect, thanks, Maxim!
>>> 
>>> -
>>> Denis
>>> 
>>> 
>>> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  
>>> wrote:
>>> 
 Folks,
 
 
 I've created an issue [1] to move all cloud-based IP-finders to the
 ignite-extensions. The motivation is the same as with migration of
 Spring Data integration - to remove integration dependency of the
 release cycle on Ignite releases.
 
 
 [1] https://issues.apache.org/jira/browse/IGNITE-15541
 
>> 
>> 
>> 
>> --
>> Best wishes,
>> Amelchev Nikita
> 
> 
>>> 
> 
> 

A new feedback has been added : 20

[Bugyard]

A new feedback has been added, go to bugyard.io to see all the details...

https://bugyard.io

A new feedback has been added 

"'folder' text should not have monospace style, only '/etc/apache-ignite'"   by 
mr.weider 

View feedback 
https://app.bugyard.io/web/app/rycqZJDyY/f/61668d9e38b0e20014ba942f

Re: Move Azure, AWS, GCE to the ignite-extensions

[Stephen Darlington]

Having extensions in Maven Central makes perfect sense for tools that need to 
be built and integrated with other code, Spring integrations for example.

That’s not the case for extensions that are required just to run Ignite. A 
self-contained zip file for each platform would work.

> On 13 Oct 2021, at 13:41, Maxim Muzafarov  wrote:
> 
> Nikolay,
> 
> All extensions will be available at the maven central for download.
> 
> Previously extensions have a dependent version on the ignite core, so
> each time the Ignite was released it made sense to include all the
> extensions into the uber-zip file. Each extension has its own release
> version now, so an extension can be upgraded and used independently,
> what is the reason include it in the single uber-zip file? Probably it
> would be better to provide a self-contained zip file for each cloud
> platform.
> 
> If I've missed your issue, so can you clarify the problem in more detail?
> 
> On Wed, 13 Oct 2021 at 14:37, Nikolay Izhikov  wrote:
>> 
>> Maxim.
>> 
>>> Currently, they are copied from the optional
>>> directory of the ignite binary package but would be copied from an
>>> appropriate ignite extension binary package.
>> 
>> But how, the user will download this binary package?
>> Right now, all the user need is Ignite distributive.
>> 
>> 
>>> 13 окт. 2021 г., в 14:32, Maxim Muzafarov  написал(а):
>>> 
>>> Stephen,
>>> 
>>> I guess the required classes of IP-finders should be in the classpath
>>> (libs directory). Currently, they are copied from the optional
>>> directory of the ignite binary package but would be copied from an
>>> appropriate ignite extension binary package. Probably I'm missing
>>> something but almost nothing changes in that process from my point of
>>> view. The documentation pages will be updated prior to the release.
>>> 
>>> On Wed, 13 Oct 2021 at 13:44, Stephen Darlington
>>>  wrote:
 
 I understand the motivation from a development point of view, but how will 
 this work for end users? Currently, the documentation talks about 
 extensions only in terms of importing maven dependencies (download.cgi 
 ). If I’m trying to 
 start a cluster on Azure, how does that work? Do I need to build my own 
 server?
 
 Regards,
 Stephen
 
> On 13 Oct 2021, at 11:35, Nikita Amelchev  wrote:
> 
> +1 to migrate and include to the Ignite 2.12 scope
> 
> пн, 20 сент. 2021 г. в 17:09, Denis Magda :
>> 
>> Perfect, thanks, Maxim!
>> 
>> -
>> Denis
>> 
>> 
>> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  
>> wrote:
>> 
>>> Folks,
>>> 
>>> 
>>> I've created an issue [1] to move all cloud-based IP-finders to the
>>> ignite-extensions. The motivation is the same as with migration of
>>> Spring Data integration - to remove integration dependency of the
>>> release cycle on Ignite releases.
>>> 
>>> 
>>> [1] https://issues.apache.org/jira/browse/IGNITE-15541
>>> 
> 
> 
> 
> --
> Best wishes,
> Amelchev Nikita
 
 
>> 

Re: Move Azure, AWS, GCE to the ignite-extensions

[Maxim Muzafarov]

Nikolay,

All extensions will be available at the maven central for download.

Previously extensions have a dependent version on the ignite core, so
each time the Ignite was released it made sense to include all the
extensions into the uber-zip file. Each extension has its own release
version now, so an extension can be upgraded and used independently,
what is the reason include it in the single uber-zip file? Probably it
would be better to provide a self-contained zip file for each cloud
platform.

If I've missed your issue, so can you clarify the problem in more detail?

On Wed, 13 Oct 2021 at 14:37, Nikolay Izhikov  wrote:
>
> Maxim.
>
> > Currently, they are copied from the optional
> > directory of the ignite binary package but would be copied from an
> > appropriate ignite extension binary package.
>
> But how, the user will download this binary package?
> Right now, all the user need is Ignite distributive.
>
>
> > 13 окт. 2021 г., в 14:32, Maxim Muzafarov  написал(а):
> >
> > Stephen,
> >
> > I guess the required classes of IP-finders should be in the classpath
> > (libs directory). Currently, they are copied from the optional
> > directory of the ignite binary package but would be copied from an
> > appropriate ignite extension binary package. Probably I'm missing
> > something but almost nothing changes in that process from my point of
> > view. The documentation pages will be updated prior to the release.
> >
> > On Wed, 13 Oct 2021 at 13:44, Stephen Darlington
> >  wrote:
> >>
> >> I understand the motivation from a development point of view, but how will 
> >> this work for end users? Currently, the documentation talks about 
> >> extensions only in terms of importing maven dependencies (download.cgi 
> >> ). If I’m trying to 
> >> start a cluster on Azure, how does that work? Do I need to build my own 
> >> server?
> >>
> >> Regards,
> >> Stephen
> >>
> >>> On 13 Oct 2021, at 11:35, Nikita Amelchev  wrote:
> >>>
> >>> +1 to migrate and include to the Ignite 2.12 scope
> >>>
> >>> пн, 20 сент. 2021 г. в 17:09, Denis Magda :
> 
>  Perfect, thanks, Maxim!
> 
>  -
>  Denis
> 
> 
>  On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  
>  wrote:
> 
> > Folks,
> >
> >
> > I've created an issue [1] to move all cloud-based IP-finders to the
> > ignite-extensions. The motivation is the same as with migration of
> > Spring Data integration - to remove integration dependency of the
> > release cycle on Ignite releases.
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-15541
> >
> >>>
> >>>
> >>>
> >>> --
> >>> Best wishes,
> >>> Amelchev Nikita
> >>
> >>
>

Re: Move Azure, AWS, GCE to the ignite-extensions

[Nikolay Izhikov]

Maxim.

> Currently, they are copied from the optional
> directory of the ignite binary package but would be copied from an
> appropriate ignite extension binary package.

But how, the user will download this binary package?
Right now, all the user need is Ignite distributive.


> 13 окт. 2021 г., в 14:32, Maxim Muzafarov  написал(а):
> 
> Stephen,
> 
> I guess the required classes of IP-finders should be in the classpath
> (libs directory). Currently, they are copied from the optional
> directory of the ignite binary package but would be copied from an
> appropriate ignite extension binary package. Probably I'm missing
> something but almost nothing changes in that process from my point of
> view. The documentation pages will be updated prior to the release.
> 
> On Wed, 13 Oct 2021 at 13:44, Stephen Darlington
>  wrote:
>> 
>> I understand the motivation from a development point of view, but how will 
>> this work for end users? Currently, the documentation talks about extensions 
>> only in terms of importing maven dependencies (download.cgi 
>> ). If I’m trying to start 
>> a cluster on Azure, how does that work? Do I need to build my own server?
>> 
>> Regards,
>> Stephen
>> 
>>> On 13 Oct 2021, at 11:35, Nikita Amelchev  wrote:
>>> 
>>> +1 to migrate and include to the Ignite 2.12 scope
>>> 
>>> пн, 20 сент. 2021 г. в 17:09, Denis Magda :
 
 Perfect, thanks, Maxim!
 
 -
 Denis
 
 
 On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  wrote:
 
> Folks,
> 
> 
> I've created an issue [1] to move all cloud-based IP-finders to the
> ignite-extensions. The motivation is the same as with migration of
> Spring Data integration - to remove integration dependency of the
> release cycle on Ignite releases.
> 
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-15541
> 
>>> 
>>> 
>>> 
>>> --
>>> Best wishes,
>>> Amelchev Nikita
>> 
>> 

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Igniters,

Scope freeze is planned for Friday, October 15.
I suggest creating the release branch on that date.

The wiki page with the release info. [1] Please, check the fix version
of your issues.

There are no unresolved blockers.
There are 3 important issues in the review state. [2]

Also, please, pay attention to unresolved documentation issues. [3]

[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
[2] 
https://issues.apache.org/jira/issues/?jql=(resolution%20%3D%20Unresolved%20AND%20project%20%3D%20%27Ignite%27%20AND%20type%20in%20(%22New%20Feature%22%2C%20Task%2C%20Sub-task%2C%20Improvement)%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20AND%20(labels%20in%20(%27important%27)%20OR%20Flags%20%3D%20Important))%20order%20by%20summary
[3] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20

пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn :
>
> I'm working on IGNITE-15504 and plan to finish it early next week.
>
> On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev  wrote:
>
> > Igniters,
> >
> > I have created the wiki page for the 2.12 release. [1]
> >
> > The release scope contains 1 issue that is marked as a blocker:
> > IGNITE-15504 .NET: SDK 2.1 is out of support, make sure project can be
> > developed with newer SDKs [2]
> >
> > Folks, do not forget to document features (65 issues still not resolved).
> > [3]
> >
> > Maxim, Ivan,
> > +1 to add these issues to the 2.12 scope.
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
> > [2] https://issues.apache.org/jira/browse/IGNITE-15504
> > [3]
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> >
> > ср, 29 сент. 2021 г. в 11:28, Ivan Daschinsky :
> > >
> > > Created issues related building ODBC module, running C++ suites and
> > > removing VS project files
> > >
> > > 1. https://issues.apache.org/jira/browse/IGNITE-15637
> > > 2.https://issues.apache.org/jira/browse/IGNITE-15636
> > >
> > > вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky :
> > >
> > > > +1
> > > >
> > > > Let's consider building odbc driver using Visual C++ 2017?
> > > >
> > > > 2015, 2017 and 2019 share the same redistributable package and it is
> > the
> > > > default one in Windows 10.
> > > >
> > > > Also, let's remove vs project files, since the most of you all agree
> > that
> > > > it is redundant.
> > > >
> > > > If both suggestions are ok, I will create ticketa soon.
> > > >
> > > > вс, 26 сент. 2021 г., 17:10 Pavel Tupitsyn :
> > > >
> > > >> +1
> > > >>
> > > >> On Fri, Sep 24, 2021 at 8:04 PM Maxim Muzafarov 
> > > >> wrote:
> > > >>
> > > >> > Hello Nikita,
> > > >> >
> > > >> > +1 if you will lead this release.
> > > >> >
> > > >> >
> > > >> > I'd suggest including into the release scope this one issue too:
> > > >> >
> > > >> > Snapshot restore must support restoring with indexes rebuild
> > > >> > https://issues.apache.org/jira/browse/IGNITE-14744
> > > >> >
> > > >> > Hopefully, it will be completed by the end of October.
> > > >> >
> > > >> > On Fri, 24 Sept 2021 at 19:48, Nikita Amelchev <
> > namelc...@apache.org>
> > > >> > wrote:
> > > >> > >
> > > >> > > Dear Ignite Community!
> > > >> > >
> > > >> > > I suggest starting Apache Ignite 2.12 release activities.
> > > >> > >
> > > >> > > For now, we've accumulated a hundred resolved issues with new
> > features
> > > >> > > and bug fixes which are waiting for their release date. For
> > example,
> > > >> > >
> > > >> > > CDC Application
> > > >> > > Index Query API
> > > >> > > Utility for analyzing indexes
> > > >> > > Java compute tasks for C++
> > > >> > > SQL commands statistics
> > > >> > > etc.
> > > >> > >
> > > >> > > I want to propose myself to be the release manager of the planning
> > > >> > release.
> > > >> > >
> > > >> > > I propose the following timeline:
> > > >> > >
> > > >> > > Scope Freeze: October 15, 2021
> > > >> > > Code Freeze: October 29, 2021
> > > >> > > Voting Date: November 15, 2021
> > > >> > > Release Date: November 22, 2021
> > > >> > >
> > > >> > > WDYT?
> > > >> > >
> > > >> > > --
> > > >> > > Best wishes,
> > > >> > > Amelchev Nikita
> > > >> >
> > > >>
> > > >
> > >
> > > --
> > > Sincerely yours, Ivan Daschinskiy
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >



-- 
Best wishes,
Amelchev Nikita

Re: Move Azure, AWS, GCE to the ignite-extensions

[Maxim Muzafarov]

Stephen,

I guess the required classes of IP-finders should be in the classpath
(libs directory). Currently, they are copied from the optional
directory of the ignite binary package but would be copied from an
appropriate ignite extension binary package. Probably I'm missing
something but almost nothing changes in that process from my point of
view. The documentation pages will be updated prior to the release.

On Wed, 13 Oct 2021 at 13:44, Stephen Darlington
 wrote:
>
> I understand the motivation from a development point of view, but how will 
> this work for end users? Currently, the documentation talks about extensions 
> only in terms of importing maven dependencies (download.cgi 
> ). If I’m trying to start 
> a cluster on Azure, how does that work? Do I need to build my own server?
>
> Regards,
> Stephen
>
> > On 13 Oct 2021, at 11:35, Nikita Amelchev  wrote:
> >
> > +1 to migrate and include to the Ignite 2.12 scope
> >
> > пн, 20 сент. 2021 г. в 17:09, Denis Magda :
> >>
> >> Perfect, thanks, Maxim!
> >>
> >> -
> >> Denis
> >>
> >>
> >> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  wrote:
> >>
> >>> Folks,
> >>>
> >>>
> >>> I've created an issue [1] to move all cloud-based IP-finders to the
> >>> ignite-extensions. The motivation is the same as with migration of
> >>> Spring Data integration - to remove integration dependency of the
> >>> release cycle on Ignite releases.
> >>>
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-15541
> >>>
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
>
>

Re: Move Azure, AWS, GCE to the ignite-extensions

[Stephen Darlington]

I understand the motivation from a development point of view, but how will this 
work for end users? Currently, the documentation talks about extensions only in 
terms of importing maven dependencies (download.cgi 
). If I’m trying to start a 
cluster on Azure, how does that work? Do I need to build my own server?

Regards,
Stephen

> On 13 Oct 2021, at 11:35, Nikita Amelchev  wrote:
> 
> +1 to migrate and include to the Ignite 2.12 scope
> 
> пн, 20 сент. 2021 г. в 17:09, Denis Magda :
>> 
>> Perfect, thanks, Maxim!
>> 
>> -
>> Denis
>> 
>> 
>> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  wrote:
>> 
>>> Folks,
>>> 
>>> 
>>> I've created an issue [1] to move all cloud-based IP-finders to the
>>> ignite-extensions. The motivation is the same as with migration of
>>> Spring Data integration - to remove integration dependency of the
>>> release cycle on Ignite releases.
>>> 
>>> 
>>> [1] https://issues.apache.org/jira/browse/IGNITE-15541
>>> 
> 
> 
> 
> -- 
> Best wishes,
> Amelchev Nikita

Re: Move Azure, AWS, GCE to the ignite-extensions

[Petr Ivanov]

+1


Those parts still very optional nowadays.

> On 20 Sep 2021, at 15:29, Maxim Muzafarov  wrote:
> 
> Folks,
> 
> 
> I've created an issue [1] to move all cloud-based IP-finders to the
> ignite-extensions. The motivation is the same as with migration of
> Spring Data integration - to remove integration dependency of the
> release cycle on Ignite releases.
> 
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-15541

Re: Move Azure, AWS, GCE to the ignite-extensions

[Nikita Amelchev]

+1 to migrate and include to the Ignite 2.12 scope

пн, 20 сент. 2021 г. в 17:09, Denis Magda :
>
> Perfect, thanks, Maxim!
>
> -
> Denis
>
>
> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  wrote:
>
> > Folks,
> >
> >
> > I've created an issue [1] to move all cloud-based IP-finders to the
> > ignite-extensions. The motivation is the same as with migration of
> > Spring Data integration - to remove integration dependency of the
> > release cycle on Ignite releases.
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-15541
> >



-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite 3.0.0-alpha3 RC1

[Pavel Tupitsyn]

-1 (binding)

Java thin client and .NET thin client are missing from the binary package.


On Wed, Oct 13, 2021 at 3:03 AM Saikat Maitra 
wrote:

> +1 (binding)
>
> Regards
> Saikat
>
> On Tue, Oct 12, 2021 at 5:03 PM Denis Magda  wrote:
>
> > +1 (binding)
> >
> > -
> > Denis
> >
> >
> > On Tue, Oct 12, 2021 at 6:01 PM Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Dear Community,
> > >
> > > Ignite 3 development is moving forward. In the last several months
> we've
> > > added the following features:
> > >
> > >- New SQL engine based on Apache Calcite + JDBC driver.
> > >- Persistence implementation based on RocksDB.
> > >- New binary client protocol with an implementation in Java.
> > >- Data rebalancing.
> > >
> > > This is a significant milestone, so I think it will be valuable to
> share
> > > the current state with the broader community.
> > >
> > > I propose to release 3.0.0 Alpha3 with the features listed above.
> > >
> > > Please vote.
> > >
> > > ---
> > >
> > > Release candidate:
> > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha3-rc1/
> > > Maven staging:
> > >
> https://repository.apache.org/content/repositories/orgapacheignite-1532
> > > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha3-rc1
> > >
> > > +1 - accept Apache Ignite 3.0.0-alpha3 RC1
> > >  0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite 3.0.0-alpha3 RC1 (explain why)
> > >
> > > Voting guidelines: https://www.apache.org/foundation/voting.html
> > > How to verify the release:
> https://www.apache.org/info/verification.html
> > >
> > > The vote will be open for 72 hours and will close on October 15th at
> 10pm
> > > UTC:
> > >
> > >
> >
> https://www.timeanddate.com/counters/fullscreen.html?mode=a&iso=20211015T15&year=2021&month=10&day=15&hour=15&min=0&sec=0&p0=224
> > >
> > > -Val
> > >
> >
>