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

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

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

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

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

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

Re: Updating Javascript npm Package

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

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

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

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

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

A new feedback has been added : 20

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

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

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

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

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,

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

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 г.,

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

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,

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

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

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

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

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

+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

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

+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 > >

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

-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,