Re[2]: Deprecating LOCAL cache

Ok, we can use node filters in such a case, i understand )   >I just dream up ) If some one have cached web session layer over >ignite with sticky cookie [1] and cross cache transaction logic through >local and global caches how this schema will transform without local ? > >[1] >https://www.im

Re: [VOTE] Release pyignite 0.5.2-rc0

+1 I checked out examples Win10 and MacOS 11 On 2021/09/10 16:08:22, Ivan Daschinsky wrote: > Dear Igniters! > > Release candidate binaries for subj are uploaded and ready for vote > You can find them here: > https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.2-rc0 > > If you follow th

Ignite Momentum: Recap of 2020-2021

Igniters, I've contributed an article listing what we, as a community, achieved together in 2020-2021: https://blogs.apache.org/ignite/entry/apache-ignite-momentum-highlights-from Apologize if I forgot to mention anything else. My goal was to share the project highlights after ASF mentioned us as

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

Ilya, > I'm still confused by this publish/ directory. Why are we shipping > something which is not for publishing in our binary package? I've also not > heard of it before. I think this was introduced in 2.8.0 as part of [1]. It is how the build process works by default and we just copy the enti

Re: Request for new TC suite

Hi, Petr! Thanks for the response. I created a ticket [1] and assigned it to you. Please have a look at it. If you have any questions please let me know. [1] https://issues.apache.org/jira/browse/IGNITE-15509 On Tue, Sep 14, 2021 at 6:05 PM Petr Ivanov wrote: > Hi, Maksim. > > > File a ticket

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

Hello! + 0.5 I have got it to run with the following command: % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 Apache.Ignite.dll I'm still confused by this publish/ directory. Why are we shipping something which is not for publishing in our binary package? I've also not heard of

Re: Request for new TC suite

Hi, Maksim. File a ticket please and I will see it through. > On 14 Sep 2021, at 17:24, Maksim Timonin wrote: > > Hi, Igniters! > > This is a request for a new TC suite. This PR [1] introduces new > functionality (IndexQuery API). I've prepared a suite [1] with tests > related to this API. I'

Request for new TC suite

Hi, Igniters! This is a request for a new TC suite. This PR [1] introduces new functionality (IndexQuery API). I've prepared a suite [1] with tests related to this API. I'd like to have an opportunity to run those tests in a separate TC suite. Currently for my PR only, and after merge it should be

Re: [VOTE] Release pyignite 0.5.2-rc0

I know you’re joking, but this iPad app claims to support third party Python libraries: https://apps.apple.com/gb/app/pyto-python-3/id1436650069 I didn’t try it but kind of curious now... > On 14 Sep 2021, at 10:40, Pavel Tupitsyn wrot

Re: [VOTE] Release pyignite 0.5.2-rc0

+1 Built from sources and run examples according to the documentation notes. On Tue, 14 Sept 2021 at 12:59, Ivan Daschinsky wrote: > > Pavel, sometimes it is impossible to use gmail service directly from you > laptop. > > вт, 14 сент. 2021 г. в 12:40, Pavel Tupitsyn : > > > > +1 > > > Отправлено

Re[2]: Deprecating LOCAL cache

I just dream up ) If some one have cached web session layer over ignite with sticky cookie [1] and cross cache transaction logic through local and global caches how this schema will transform without local ?   [1]  https://www.imperva.com/learn/availability/sticky-session-persistence-and-cookie

Re: Deprecating LOCAL cache

I agree with Ivan, let's return an error on any attempt to create or use a LOCAL cache from thin clients. On Tue, Sep 14, 2021 at 2:25 PM Ivan Daschinsky wrote: > I am not about creation per se, but creation from a thin client side. > > This feature simply doesn't work as expected, broken and im

Re: Deprecating LOCAL cache

I am not about creation per se, but creation from a thin client side. This feature simply doesn't work as expected, broken and impossible to fix. It cannot broke any code, because it was already broken and it is impossible to use in production. But it still can embarrass newcomers and brings a lot

Re: Deprecating LOCAL cache

Ivan, I don't think we should rush with this. Banning the creation of LOCAL caches without a warning through the code sounds not good. Will it be better to do everything in three steps (releases)? 2.12 deprecate, 2.13 forbid new cache creation, 2.14 remove. On Tue, 14 Sept 2021 at 12:09, Ivan Das

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

Folks, > Maxim, should we fix it and rebuild RC? I've cherry-picked the [1] issue to the release branch. This will not require rebuilding the RC since the issue is related to the documentation task. [1] https://issues.apache.org/jira/browse/IGNITE-15503 On Tue, 14 Sept 2021 at 12:37, Pavel Tupi

Re: [VOTE] Release pyignite 0.5.2-rc0

Pavel, sometimes it is impossible to use gmail service directly from you laptop. вт, 14 сент. 2021 г. в 12:40, Pavel Tupitsyn : > > +1 > > Отправлено с iPhone > > Nikolay, did you test pyignite from your iPhone? Does it work? :) > > On Tue, Sep 14, 2021 at 12:22 PM Николай Ижиков > wrote: > > >

Re: [VOTE] Release pyignite 0.5.2-rc0

> +1 > Отправлено с iPhone Nikolay, did you test pyignite from your iPhone? Does it work? :) On Tue, Sep 14, 2021 at 12:22 PM Николай Ижиков wrote: > +1 > > Отправлено с iPhone > > > 14 сент. 2021 г., в 11:39, Pavel Tupitsyn > написал(а): > > > > +1 > > > > Checked on Ubuntu 20.04, ran a few

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

Ilya, > When I have also installed 3.1 and 2.0 Please try .NET SDK 2.1 to run tests. Yes, it went out of support last month, I've created a ticket [1]. > dotnet Apache.Ignite.dll That's correct, but should be done in platforms/dotnet/bin/netcoreapp2.0/publish, please try again. We should deal wi

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

> check again, 15503 not cherry-pick, right? Yes, the above ticket is not in the ignite-2.11 branch. Maxim, should we fix it and rebuild RC? вт, 14 сент. 2021 г. в 11:58, Ilya Kasnacheev : > Hello! > > - 0.5 > > Installed DEB package, built binary from source, ran sqlline, built .NET. > > I have

Re: [VOTE] Release pyignite 0.5.2-rc0

+1 checked out examples Win10 with pyignite-0.5.2-cp38-cp38-win_amd64.whl вт, 14 сент. 2021 г. в 12:22, Николай Ижиков : > +1 > > Отправлено с iPhone > > > 14 сент. 2021 г., в 11:39, Pavel Tupitsyn > написал(а): > > > > +1 > > > > Checked on Ubuntu 20.04, ran a few examples. > > > >> On Tue, S

Re: [VOTE] Release pyignite 0.5.2-rc0

+1 Отправлено с iPhone > 14 сент. 2021 г., в 11:39, Pavel Tupitsyn написал(а): > > +1 > > Checked on Ubuntu 20.04, ran a few examples. > >> On Tue, Sep 14, 2021 at 11:12 AM Ivan Daschinsky >> wrote: >> >> +1 from me >> Checked on windows 10 x86_64 (visual studio 2017) and ubuntu 20.04 x86_

Re: Deprecating LOCAL cache

Few thoughts about LOCAL caches on thin client: 1. If partition awareness is disabled: a. Inconsistent behaviour if node to which client is connected goes down. 2. If partition awareness is enabled: a. For Java and .NET -- same as 1a b. For C++ and python -- use random routing for caches that are

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

Hello! - 0.5 Installed DEB package, built binary from source, ran sqlline, built .NET. I have failed to run .NET tests though. If I only install Current .NET, I get the following: It was not possible to find any compatible framework version The framework 'Microsoft.NETCore.App', version '2.0.0'

Re: [VOTE] Release pyignite 0.5.2-rc0

+1 Checked on Ubuntu 20.04, ran a few examples. On Tue, Sep 14, 2021 at 11:12 AM Ivan Daschinsky wrote: > +1 from me > Checked on windows 10 x86_64 (visual studio 2017) and ubuntu 20.04 x86_64 > and on pythons 3.6, 3.7, 3.8, 3.9 (both win and linux): > 1. Installing from source -- passe > 2. Bu

Re: Deprecating LOCAL cache

>> Unsupported operation exception. Binary protocol doesn't have a concept of exception, only error status and message, but it is just a remark I suppose that response with error status and message is ok, but may be others have different opinion? >> Removal should happen at 2.13. A few thin client

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

check again, 15503 not cherry-pick, right? 在 2021/9/14 15:55, Shishkov Ilya 写道: Should the following two issue be merged into the ignite-2.11 branch? Hi, as I see, both tickets are fixed in 2.10 and 2.11. вт, 14 сент. 2021 г. в 04:13, 18624049226<18624049...@163.com>: Should the following tw

Re: Deprecating LOCAL cache

> 1. What is expected behaviour if an old thin client requests creation of > LOCAL cache on the newest ignite cluster? Unsupported operation exception. > 2. Should we completely remove LOCAL caches support in thin clients (i.e. pyignite) before 2.13 release? Removal should happen at 2.13. On Tue,

Re: [VOTE] Release pyignite 0.5.2-rc0

+1 from me Checked on windows 10 x86_64 (visual studio 2017) and ubuntu 20.04 x86_64 and on pythons 3.6, 3.7, 3.8, 3.9 (both win and linux): 1. Installing from source -- passe 2. Building wheels from source -- passed 3. Installing wheels -- passed Checked on each steps C module and examples. -- pa

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

> Should the following two issue be merged into the ignite-2.11 branch? Hi, as I see, both tickets are fixed in 2.10 and 2.11. вт, 14 сент. 2021 г. в 04:13, 18624049226 <18624049...@163.com>: > Should the following two issue be merged into the ignite-2.11 branch? > > https://issues.apache.org/ji

Re: Deprecating LOCAL cache

>> 2. 2.13 - complete removal LOCAL caches from codebase. Let's discuss this step with more details. 1. What is expected behaviour if an old thin client requests creation of LOCAL cache on the newest ignite cluster? 2. Should we completely remove LOCAL caches support in thin clients (i.e. pyignite)

Re: Deprecating LOCAL cache

I proposed the following plan: 1. 2.12 - deprecation of LOCAL caches. 2. 2.13 - complete removal LOCAL caches from codebase. > 13 сент. 2021 г., в 13:30, Ivan Daschinsky написал(а): > > I personally support deprecation, but we should at least have a plan. > I suppose that putting annotations a