Re: [VOTE] Release Apache Ignite 3.0.0-alpha4 RC1
+1 (binding) On Wed, Jan 26, 2022 at 4:46 PM Denis Magda wrote: > > +1 (binding) > > — > Denis > > > On Jan 25, 2022, at 2:44 PM, Valentin Kulichenko > > wrote: > > > > Dear Community, > > > > Ignite 3 is moving forward and I think we're in a good spot to release > > another alpha version. In the last few month the following major features > > have been added: > > > > - Transactional API > > - Record and KeyValue views with POJO mapping support > > - DDL > > > > 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 > > Alpha4 with the features listed above. > > > > Please vote. > > > > --- > > > > Release candidate: > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha4-rc1/ > > Maven staging: > > https://repository.apache.org/content/repositories/orgapacheignite-1540/ > > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha4-rc1 > > > > +1 - accept Apache Ignite 3.0.0-alpha4 RC1 > > 0 - don't care either way > > -1 - DO NOT accept Apache Ignite 3.0.0-alpha4 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 January 28th at 8pm > > UTC: https://www.timeanddate.com/countdown/to?iso=20220128T12=224 > > > > -Val
Re: Move Azure, AWS, GCE to the ignite-extensions
Do we know what happened with this thread? I just saw a question in the user list asking about where the ignite-aws-ext module is now that Ignite 2.12 is out. Regards, Stephen > On 24 Nov 2021, at 11:11, Maxim Muzafarov wrote: > > Petr, > > There is only the GCE suite left to be configured. I've created an > issue [1] to do this. Please, take a look. > > [1] https://issues.apache.org/jira/browse/IGNITE-15981 > > On Wed, 24 Nov 2021 at 12:00, Petr Ivanov wrote: >> >> Hi, Maksim. >> >> >> Can you file a ticket about recreating test suites for extensions, please? >> I will attend to it in nearest time. >> >> >>> On 23 Nov 2021, at 17:14, Maxim Muzafarov wrote: >>> >>> Hello Petr, >>> >>> Can you assist me with configuring the GCE [1] suite on the TC >>> Extensions project? Currently, I have an issue with moving environment >>> variables from the old GCE suite [2] to the new one. >>> >>> I need to create the following envs: >>> - env.test.gce.account.id >>> - env.test.gce.p12.path >>> - env.test.gce.project.name >>> >>> However the `id` seems to be a password, so it's hidden on the admin >>> panel. Can you please help me with this? >>> >>> [1] >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Gce_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv >>> [2] >>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_GceOld_IgniteTests24Java8=ignite-2.12=buildTypeStatusDiv >>> >>> On Mon, 25 Oct 2021 at 14:22, Maxim Muzafarov wrote: Folks, I've moved the azure, gce, aws modules to the ignite-extensions project. https://issues.apache.org/jira/browse/IGNITE-15541 Building the modules in the ignite-extension project will prepare an appropriate release zip file containing all the necessary dependencies: - ignite-aws-ext.zip - ignite-gce-ext.zip - ignite-auzre-ext.zip On Wed, 13 Oct 2021 at 17:09, Stephen Darlington wrote: > > 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?
Re: Nabble forum scheduled for deletion
Thank you, Denis! In that case, I agree we can ignore the notification. ср, 26 янв. 2022 г. в 17:07, Denis Magda : > Open this link and read the text in red, I put it together with some other > community members after Nabble informed us about the plans to downsize all > the forums: > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/ > > Now, as long as nobody uses that legacy forum, Nabble wants to delete it > completely. Let them do that, you can ignore the current notice about the > inactivity and deletion. Again, that’s just a UI, real archives are stored > on the ASF side. > > — > Denis > > > On Jan 26, 2022, at 9:03 AM, Denis Magda wrote: > > > > Hey, > > > > Nabble turns off all the forums trying to reduce their costs. Same what > we had with the user list a few months ago. We store admin credentials in a > special PMC folder on SVN. I can send the URL later if you don’t what that > is. > > > > There is no need to archive/download anything from Nabble. That was just > a UI for our user/dev mail archives. Now we can use pony mail. > > > > > > > > — > > Denis > > > >> On Jan 26, 2022, at 3:32 AM, Kseniya Romanova > wrote: > >> > >> As I understand from their forum nibble mark for deletion all forums > which > >> have had no activity for three months and the archive is disconnected > from > >> the updates. Does anyone have admin access to nibble? Probably we can at > >> least download the archive to save before we find an alternative > solution. > >> > >> Kseniya > >> > >> ср, 26 янв. 2022 г. в 11:18, Ilya Kasnacheev >: > >> > >>> Hello! > >>> > >>> It would be a pity if they delete that, but I can't see any > instructions > >>> there. > >>> > >>> Regards, > >>> -- > >>> Ilya Kasnacheev > >>> > >>> > >>> вт, 25 янв. 2022 г. в 18:22, Nabble : > >>> > > Dear Nabble user, > > The forum listed below is inactive and has been scheduled for > deletion in > 30 days. > To prevent this forum from being deleted, visit the forum and follow > the > instructions. > > > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/ > > If this forum is deleted, your posts in this forum will be deleted. > You can see your posts here: > > > > >>> > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/template/NamlServlet.jtp?macro=user_nodes=1 > > ** For more information, see: > http://s1.nabble.com/help/Answer.jtp?id=53 > > Regards, > The Nabble team > > >>> >
Re: Nabble forum scheduled for deletion
Open this link and read the text in red, I put it together with some other community members after Nabble informed us about the plans to downsize all the forums: http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/ Now, as long as nobody uses that legacy forum, Nabble wants to delete it completely. Let them do that, you can ignore the current notice about the inactivity and deletion. Again, that’s just a UI, real archives are stored on the ASF side. — Denis > On Jan 26, 2022, at 9:03 AM, Denis Magda wrote: > > Hey, > > Nabble turns off all the forums trying to reduce their costs. Same what we > had with the user list a few months ago. We store admin credentials in a > special PMC folder on SVN. I can send the URL later if you don’t what that is. > > There is no need to archive/download anything from Nabble. That was just a UI > for our user/dev mail archives. Now we can use pony mail. > > > > — > Denis > >> On Jan 26, 2022, at 3:32 AM, Kseniya Romanova wrote: >> >> As I understand from their forum nibble mark for deletion all forums which >> have had no activity for three months and the archive is disconnected from >> the updates. Does anyone have admin access to nibble? Probably we can at >> least download the archive to save before we find an alternative solution. >> >> Kseniya >> >> ср, 26 янв. 2022 г. в 11:18, Ilya Kasnacheev : >> >>> Hello! >>> >>> It would be a pity if they delete that, but I can't see any instructions >>> there. >>> >>> Regards, >>> -- >>> Ilya Kasnacheev >>> >>> >>> вт, 25 янв. 2022 г. в 18:22, Nabble : >>> Dear Nabble user, The forum listed below is inactive and has been scheduled for deletion in 30 days. To prevent this forum from being deleted, visit the forum and follow the instructions. http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/ If this forum is deleted, your posts in this forum will be deleted. You can see your posts here: >>> http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/template/NamlServlet.jtp?macro=user_nodes=1 ** For more information, see: http://s1.nabble.com/help/Answer.jtp?id=53 Regards, The Nabble team >>>
Re: Nabble forum scheduled for deletion
Hey, Nabble turns off all the forums trying to reduce their costs. Same what we had with the user list a few months ago. We store admin credentials in a special PMC folder on SVN. I can send the URL later if you don’t what that is. There is no need to archive/download anything from Nabble. That was just a UI for our user/dev mail archives. Now we can use pony mail. — Denis > On Jan 26, 2022, at 3:32 AM, Kseniya Romanova wrote: > > As I understand from their forum nibble mark for deletion all forums which > have had no activity for three months and the archive is disconnected from > the updates. Does anyone have admin access to nibble? Probably we can at > least download the archive to save before we find an alternative solution. > > Kseniya > > ср, 26 янв. 2022 г. в 11:18, Ilya Kasnacheev : > >> Hello! >> >> It would be a pity if they delete that, but I can't see any instructions >> there. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> вт, 25 янв. 2022 г. в 18:22, Nabble : >> >>> >>> Dear Nabble user, >>> >>> The forum listed below is inactive and has been scheduled for deletion in >>> 30 days. >>> To prevent this forum from being deleted, visit the forum and follow the >>> instructions. >>> >>> http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/ >>> >>> If this forum is deleted, your posts in this forum will be deleted. >>> You can see your posts here: >>> >>> >>> >> http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/template/NamlServlet.jtp?macro=user_nodes=1 >>> >>> ** For more information, see: >>> http://s1.nabble.com/help/Answer.jtp?id=53 >>> >>> Regards, >>> The Nabble team >>> >>
Re: [VOTE] Release Apache Ignite 3.0.0-alpha4 RC1
+1 (binding) — Denis > On Jan 25, 2022, at 2:44 PM, Valentin Kulichenko > wrote: > > Dear Community, > > Ignite 3 is moving forward and I think we're in a good spot to release > another alpha version. In the last few month the following major features > have been added: > > - Transactional API > - Record and KeyValue views with POJO mapping support > - DDL > > 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 > Alpha4 with the features listed above. > > Please vote. > > --- > > Release candidate: > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha4-rc1/ > Maven staging: > https://repository.apache.org/content/repositories/orgapacheignite-1540/ > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha4-rc1 > > +1 - accept Apache Ignite 3.0.0-alpha4 RC1 > 0 - don't care either way > -1 - DO NOT accept Apache Ignite 3.0.0-alpha4 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 January 28th at 8pm > UTC: https://www.timeanddate.com/countdown/to?iso=20220128T12=224 > > -Val
Re: [VOTE] Release Apache Ignite 3.0.0-alpha4 RC1
+1 (binding) Best Regards, Igor On Tue, Jan 25, 2022 at 10:44 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > +1 (binding) > > On Tue, Jan 25, 2022 at 11:43 AM Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Dear Community, > > > > Ignite 3 is moving forward and I think we're in a good spot to release > > another alpha version. In the last few month the following major features > > have been added: > > > >- Transactional API > >- Record and KeyValue views with POJO mapping support > >- DDL > > > > 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 > > Alpha4 with the features listed above. > > > > Please vote. > > > > --- > > > > Release candidate: > > https://dist.apache.org/repos/dist/dev/ignite/3.0.0-alpha4-rc1/ > > Maven staging: > > https://repository.apache.org/content/repositories/orgapacheignite-1540/ > > Git tag: https://github.com/apache/ignite-3/tree/3.0.0-alpha4-rc1 > > > > +1 - accept Apache Ignite 3.0.0-alpha4 RC1 > > 0 - don't care either way > > -1 - DO NOT accept Apache Ignite 3.0.0-alpha4 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 January 28th at 8pm > > UTC: https://www.timeanddate.com/countdown/to?iso=20220128T12=224 > > > > -Val > > >
Re: Proxy (GridServiceProxy) for local services if required
Vladimir, I think we should make the same changes to the .NET API.
On Tue, Jan 25, 2022 at 5:17 PM Vladimir Steshin wrote:
> Similar question about .NET. I'm doing the sub-ticket with metrics
> of the platform services. Should we return proxy every tome by
> /IServices.GerServiceProxy()/ and probably deprecate
> /IServices.GetService()/. Same problems with variate the behavior of
> /GerServiceProxy()/ and statistics corruption (if enabled) with
> /GetService()/.
>
> 24.01.2022 22:27, Valentin Kulichenko пишет:
> > Vladimir,
> >
> > Agreed. My point is that the actual issue we want to fix is broken
> metrics.
> > Thus, we should have a single ticket/patch *about the broken metrics*
> that
> > incorporates all required changes, as well as relevant documentation
> > updates.
> >
> > I don't think we need a vote. I will also change mine to +1 in the
> existing
> > thread.
> >
> > -Val
> >
> > On Mon, Jan 24, 2022 at 11:23 AM Vladimir Steshin
> > wrote:
> >
> >> Sure. This is a simple change. These 2 fixes could go together.
> And
> >> the doc already has notes of service statistics traits. Ok, might be
> >> even better.
> >>
> >> I'm not sure whether we need extra voting for deprecating
> >> 'service()' and, as earlier and making 'serviceProxy()' return proxy
> >> every time. Several active contributors have said their 'yes' for both
> >> in the thread.
> >>
> >> Several active contributors have already said their 'yes'.
> >>
> >> 23.01.2022 03:50, Valentin Kulichenko пишет:
> >>> If we already agreed to deprecate the service() method, then I'm ok
> with
> >>> the change. But I think we should do both fixes together and also
> clearly
> >>> document that using service() can lead to incorrect metrics.
> >>>
> >>> -Val
> >>>
> >>> On Fri, Jan 21, 2022 at 1:13 AM Vladimir Steshin
> >> wrote:
> Valentin, there are 2 notable issues:
>
> 1) Variate behavior of `/serviceProxy()/` depending on user setting.
> It
> can return both proxy and reference.
>
> 2) Service metrics are corrupted by invocations through `/service()/`.
>
>
> How we can fix:
>
> 1) Just return proxy every time.
>
> 2) Deprecate `/service()/`. We've already discussed that here: [1].
> Please see my previous message in the thread.
>
>
>
> [1]https://www.mail-archive.com/dev@ignite.apache.org/msg44062.html
>
>
> On 20.01.2022 22:48, Valentin Kulichenko wrote:
> > So the proposed change will not actually fix the issue with metrics,
> > because it's still possible to get a local instance via the service()
> > method. At the same time, the change removes an existing performance
> > optimization.
> >
> > Let's figure out how to fix the actual problem. If the *only* way to
> >> have
> > metrics is to have a proxy, then this should be the only way to
> >> interact
> > with a service. In that case, we need to do something with the
> >> service()
> > method (deprecate it?). Or probably there are other ways to fix
> >> metrics?
> > -Val
> >
> > On Thu, Jan 20, 2022 at 3:32 AM Vladimir Steshin
> wrote:
> >> Yes. Invocations from direct reference are not measured. This
> >> method
> >> in the javadoc:
> >>
> >>
> >> /* NOTE: Statistics are collected only with service proxies
> >> obtaining by methods like/
> >>
> >> /* {@link IgniteServices#serviceProxy(String, Class, boolean)} and
> >> won't
> >> work for direct reference of local/
> >>
> >> /* services which you can get by, for example, {@link
> >> IgniteServices#service(String)}./
> >>
> >>
> >> On 20.01.2022 00:20, Valentin Kulichenko wrote:
> >>> BTW, there is also the service() method that can only return an
> instance
> >>> and never returns a proxy. Does it corrupt the metrics as well?
> >>>
> >>> -Val
> >>>
> >>> On Wed, Jan 19, 2022 at 1:09 PM Valentin Kulichenko <
> >>> valentin.kuliche...@gmail.com> wrote:
> >>>
> Maxim,
>
> The reason I'm asking is that I don't really understand how client
> side
> mechanics affect server side metrics (number of executions and
> their
> durations). I feel that we might be fixing a wrong problem.
>
> Could you elaborate on why we count metrics incorrectly when
> the serviceProxy() returns an instance of a local service instead
> of
> an
> actual proxy?
>
> -Val
>
> On Tue, Jan 18, 2022 at 11:32 PM Maksim Timonin<
> timoninma...@apache.org
> wrote:
>
> > Hi, guys!
> >
> >> this is not a good idea to change the behavior of serviceProxy()
> > depending on statistics
> >
> > I think that the patch doesn't change the behavior of
> `serviceProxy()`.
> > This method promises a
Re: Nabble forum scheduled for deletion
As I understand from their forum nibble mark for deletion all forums which have had no activity for three months and the archive is disconnected from the updates. Does anyone have admin access to nibble? Probably we can at least download the archive to save before we find an alternative solution. Kseniya ср, 26 янв. 2022 г. в 11:18, Ilya Kasnacheev : > Hello! > > It would be a pity if they delete that, but I can't see any instructions > there. > > Regards, > -- > Ilya Kasnacheev > > > вт, 25 янв. 2022 г. в 18:22, Nabble : > > > > > Dear Nabble user, > > > > The forum listed below is inactive and has been scheduled for deletion in > > 30 days. > > To prevent this forum from being deleted, visit the forum and follow the > > instructions. > > > > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/ > > > > If this forum is deleted, your posts in this forum will be deleted. > > You can see your posts here: > > > > > > > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/template/NamlServlet.jtp?macro=user_nodes=1 > > > > ** For more information, see: > > http://s1.nabble.com/help/Answer.jtp?id=53 > > > > Regards, > > The Nabble team > > >
Re: Nabble forum scheduled for deletion
Hello! It would be a pity if they delete that, but I can't see any instructions there. Regards, -- Ilya Kasnacheev вт, 25 янв. 2022 г. в 18:22, Nabble : > > Dear Nabble user, > > The forum listed below is inactive and has been scheduled for deletion in > 30 days. > To prevent this forum from being deleted, visit the forum and follow the > instructions. > > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/ > > If this forum is deleted, your posts in this forum will be deleted. > You can see your posts here: > > > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/template/NamlServlet.jtp?macro=user_nodes=1 > > ** For more information, see: > http://s1.nabble.com/help/Answer.jtp?id=53 > > Regards, > The Nabble team >
