Re: [DISCUSSION] Change default behaviour of atomic operations inside transactions

Ok, let's do this. And schedule the fix to the 2.16. On Mon, Oct 17, 2022 at 7:42 PM Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > By placing the @Deprecated annotation on the property. > > пн, 17 окт. 2022 г. в 19:07, Anton Vinogradov : > > > How can we deprecate this? > > > > On Mo

Re: Ignite support for IoC beyond spring framework

Going forward over evaluation - I think for naming consistency reasons we shall stay with @InjectResource cause other annotations which bring outside values are @SpringResource, @LoggerResource and @IgniteInstanceResource. Making it @IgniteInject is fine for me too, but it might not fit into

Re: [DISCUSSION] Change default behaviour of atomic operations inside transactions

By placing the @Deprecated annotation on the property. пн, 17 окт. 2022 г. в 19:07, Anton Vinogradov : > How can we deprecate this? > > On Mon, Oct 17, 2022 at 5:30 PM Alexei Scherbakov < > alexey.scherbak...@gmail.com> wrote: > > > We can do breaking changes by following the approved procedure:

Re: [Sugestion] Switching ignite scheduler to cron-utils

Hello Ilya, Thank you for clarification. I wasn't aware schedule is on strike. ;-) Mentioned cron-utils is something I used. My intention was to reduce number of profiles needed to build ignite, but if this module is marked for removal then both - an extra profile and licensing inconsistency wi

Re: [Sugestion] Switching ignite scheduler to cron-utils

Hello! I suggest getting rid of ignite scheduler completely. It is poorly thought out, not used by anyone, has a baroque and incomplete API. In no way it is doing anything useful for out users in its current form. Yes we could rewrite it to be more useful, but I think Ignite is not a distributed

Re: [DISCUSSION] Change default behaviour of atomic operations inside transactions

How can we deprecate this? On Mon, Oct 17, 2022 at 5:30 PM Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > We can do breaking changes by following the approved procedure: 1) > deprecate in the next release 2) remove in the some release after the next > > The ticket looks fine to me. >

[Sugestion] Switching ignite scheduler to cron-utils

One of projects I recently worked with found a ASLv2 compatible library which allows to parse CRON expressions and host scheduler calls: https://github.com/jmrozanec/cron-utils Maybe it could help making ignite library/license handling more consistent. Best, Łukasz

Re: Ignite support for IoC beyond spring framework

I created https://issues.apache.org/jira/browse/IGNITE-17915. Going to try updating code and see how much impact it will have. Best, Łukasz On 14.10.2022 20:21, Łukasz Dywicki wrote: Hello Semyon, I wasn't sure if deprecation of @SpringResource would be acceptable, if so It gives us more flexi

Re: [DISCUSSION] Change default behaviour of atomic operations inside transactions

We can do breaking changes by following the approved procedure: 1) deprecate in the next release 2) remove in the some release after the next The ticket looks fine to me. пн, 17 окт. 2022 г. в 15:50, Anton Vinogradov : > We MUST break this, of course! > Atomic operations inside the transaction i

Re: [DISCUSSION] Change default behaviour of atomic operations inside transactions

We MUST break this, of course! Atomic operations inside the transaction is a wrong and unexpected behaviour and MUST be restricted for every user. On Mon, Oct 17, 2022 at 3:05 PM Julia Bakulina wrote: > Hi Team, > > I have found this ticket https://issues.apache.org/jira/browse/IGNITE-8801 - > C

[DISCUSSION] Change default behaviour of atomic operations inside transactions

Hi Team,   I have found this ticket https://issues.apache.org/jira/browse/IGNITE-8801 - Change default behaviour of atomic operations inside transactions - in backlog and created a PR with changes. The ticket relates to  https://issues.apache.org/jira/browse/IGNITE-2313. During the review process