Re: [VOTE] Release pyignite 0.5.2-rc0

[Aleksandr Nikolaev]

+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 the link above, you will find source packages (*.tar.gz and
> *.zip)
> and binary packages (wheels) for windows (amd64) and linux (x86_64)
> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.
> Code signing keys can be found here --
> https://downloads.apache.org/ignite/KEYS
> Here you can find instructions how to verify packages
> https://www.apache.org/info/verification.html
>
> You can install binary package for specific version of python using pip
> For example do this on linux for python 3.8
> >> pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
>
> You can build and install package from source using this command:
> >> pip install pyignite-0.5.2.tar.gz
> You can build wheel on your platform using this command:
> >> pip wheel --no-deps pyignite-0.5.2.tar.gz
>
> For building C module, you should have python headers and C compiler
> installed.
> (i.e. for ubuntu sudo apt install build-essential python3-dev)
> In Mac OS X xcode-tools and python from homebrew are the best option.
>
> In order to check whether C module works, use following:
> >> from pyignite import _cutils
> >> print(_cutils.hashcode('test'))
> >> 3556498
>
> You can find documentation here:
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
>
> You can find examples here (to check them, you should start ignite 
locally):
> 
https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html

> Also, examples can be found in source archive in examples subfolder.
> docker-compose.yml is supplied in order to start ignite quickly. (Use
> `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> down` to shut down it)
>
> Release notes:
> 
https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76

>
> Git release tag was created:
> 
https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0

>
> The vote is formal, see voting guidelines
> https://www.apache.org/foundation/voting.html
>
> +1 - to accept pyignite-0.5.2-rc0
> 0 - don't care either way
> -1 - DO NOT accept pyignite-0.5.2-rc0
>
> The vote finishes at 09/15/2021 15:00 UTC
>

Ignite Momentum: Recap of 2020-2021

[Denis Magda]

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 a top 5 project in the recent
FY2021 report.

Please share through social media.

-
Denis

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[Pavel Tupitsyn]

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 entire
bin directory to the package,
while only publish subdir is actually required.

We can probably drop support for legacy (unsupported) .NET versions in the
next release and simplify our build process, I'll look into this.

[1] https://issues.apache.org/jira/browse/IGNITE-11805

On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev 
wrote:

> 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 it before.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn :
>
> > 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 with duplicate binaries, I've created another ticket [2]
> >
> >
> > > Why do we still ship Apache.Ignite.exe if it does not run?
> > It runs on Windows. For Linux we ship Apache.Ignite.dll.
> >
> >
> > I don't think any of this is a blocker for the current release.
> > - Out-of-support SDK only affects those who build from source, and it
> went
> > out of support only recently
> > - Duplicate binaries are there for a long time and no one was complaining
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-15504
> > [2] https://issues.apache.org/jira/browse/IGNITE-15505
> >
> > On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com>
> > wrote:
> >
> > > 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' was not found.
> > >
> > >
> > >  - The following frameworks were found:
> > >
> > >
> > >  5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App]
> > >
> > >
> > > You can resolve the problem by installing the specified framework
> and/or
> > > SDK.
> > >
> > >
> > > The specified framework can be found at:
> > >
> > >
> > >  -
> > >
> > >
> >
> https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App_version=2.0.0=x64=ubuntu.21.04-x64
> > >
> > > When I have also installed 3.1 and 2.0, now I see:
> > >
> > > The active test run was aborted. Reason: Test host process crashed : No
> > > usable version of the libssl was found
> > >
> > > It looks like we have to bump the permitted .NET version.
> > >
> > > From the slim binary package I also can't run .NET:
> > >
> > > ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0%
> > > dotnet Apache.Ignite.dll
> > > Error:
> > >  An assembly specified in the application dependencies manifest
> > > (Apache.Ignite.deps.json) was not found:
> > >package: 'System.Configuration.ConfigurationManager', version:
> '4.4.0'
> > >path:
> > 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll'
> > >
> > > Do we have any instructions on how to run it under Linux? Why do we
> still
> > > ship Apache.Ignite.exe if it does not run?
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>:
> > >
> > > > 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 two issue be merged into the ignite-2.11
> > branch?
> > > > >>
> > > > >> https://issues.apache.org/jira/browse/IGNITE-14404
> > > > >>
> > > > >> https://issues.apache.org/jira/browse/IGNITE-15503
> > > > >>
> > > > >> 在 2021/9/13 17:12, Pavel Tupitsyn 写道:
> > > > >>> +1
> > > > >>>
> > > > >>> Downloaded binary packages, started a cluster with a few nodes,
> > > tested
> > > > >> new
> > > > >>> .NET examples.
> > > > >>>
> > > > >>> On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
> > > > >>>wrote:
> > > > >>>
> > > >  Thanks Maxim !
> > > >  I tries to compare this ver with 2.10 (some performance tests
> with
> > > >  persistence and transactional\atomic 

Re: Request for new TC suite

[Maksim Timonin]

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 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'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
> > enabled for the master branch.
> >
> > How can I do this?
> >
> > Thanks!
> >
> > [1] https://github.com/apache/ignite/pull/9118
> > [2] Path is
> >
> ./modules/indexing/src/test/java/org/apache/ignite/cache/query/IndexQueryTestSuite.java
>
>

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[Ilya Kasnacheev]

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 it before.

Regards,
-- 
Ilya Kasnacheev


вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn :

> 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 with duplicate binaries, I've created another ticket [2]
>
>
> > Why do we still ship Apache.Ignite.exe if it does not run?
> It runs on Windows. For Linux we ship Apache.Ignite.dll.
>
>
> I don't think any of this is a blocker for the current release.
> - Out-of-support SDK only affects those who build from source, and it went
> out of support only recently
> - Duplicate binaries are there for a long time and no one was complaining
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15504
> [2] https://issues.apache.org/jira/browse/IGNITE-15505
>
> On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com>
> wrote:
>
> > 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' was not found.
> >
> >
> >  - The following frameworks were found:
> >
> >
> >  5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App]
> >
> >
> > You can resolve the problem by installing the specified framework and/or
> > SDK.
> >
> >
> > The specified framework can be found at:
> >
> >
> >  -
> >
> >
> https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App_version=2.0.0=x64=ubuntu.21.04-x64
> >
> > When I have also installed 3.1 and 2.0, now I see:
> >
> > The active test run was aborted. Reason: Test host process crashed : No
> > usable version of the libssl was found
> >
> > It looks like we have to bump the permitted .NET version.
> >
> > From the slim binary package I also can't run .NET:
> >
> > ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0%
> > dotnet Apache.Ignite.dll
> > Error:
> >  An assembly specified in the application dependencies manifest
> > (Apache.Ignite.deps.json) was not found:
> >package: 'System.Configuration.ConfigurationManager', version: '4.4.0'
> >path:
> 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll'
> >
> > Do we have any instructions on how to run it under Linux? Why do we still
> > ship Apache.Ignite.exe if it does not run?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>:
> >
> > > 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 two issue be merged into the ignite-2.11
> branch?
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-14404
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-15503
> > > >>
> > > >> 在 2021/9/13 17:12, Pavel Tupitsyn 写道:
> > > >>> +1
> > > >>>
> > > >>> Downloaded binary packages, started a cluster with a few nodes,
> > tested
> > > >> new
> > > >>> .NET examples.
> > > >>>
> > > >>> On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
> > > >>>wrote:
> > > >>>
> > >  Thanks Maxim !
> > >  I tries to compare this ver with 2.10 (some performance tests with
> > >  persistence and transactional\atomic payload) and seems all ok
> > there.
> > >  +1 from me.
> > > 
> > > > Dear Community,
> > > >
> > > >
> > > > The release candidate for the 2.11 version is ready.
> > > >
> > > >
> > > > I have uploaded a release candidate to:
> > > > https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
> > > >
> https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/
> > > >
> > > > The following staging can be used for testing:
> > > >
> > > >>
> > >
> https://repository.apache.org/content/repositories/orgapacheignite-1526/
> > > >>
> > >
> >
> https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
> > > > Tag name is 2.11.0-rc2:
> > > >
> > > >>
> > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2
> > > > RELEASE_NOTES:
> > > >
> > > >>
> > >
> >
> 

Re: Request for new TC suite

[Petr Ivanov]

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'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
> enabled for the master branch.
> 
> How can I do this?
> 
> Thanks!
> 
> [1] https://github.com/apache/ignite/pull/9118
> [2] Path is
> ./modules/indexing/src/test/java/org/apache/ignite/cache/query/IndexQueryTestSuite.java

Request for new TC suite

[Maksim Timonin]

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
enabled for the master branch.

How can I do this?

Thanks!

[1] https://github.com/apache/ignite/pull/9118
[2] Path is
./modules/indexing/src/test/java/org/apache/ignite/cache/query/IndexQueryTestSuite.java

Re: [VOTE] Release pyignite 0.5.2-rc0

[Stephen Darlington]

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  wrote:
> 
>> +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 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. Building wheels from source -- passed
 3. Installing wheels -- passed
 
 Checked on each steps C module and examples. -- passed
 
 Checked hashsums and gpg signatures -- passed
 
 пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :
 
> 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 the link above, you will find source packages (*.tar.gz
>> and
> *.zip)
> and binary packages (wheels) for windows (amd64) and linux (x86_64)
> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.
> Code signing keys can be found here --
> https://downloads.apache.org/ignite/KEYS
> Here you can find instructions how to verify packages
> https://www.apache.org/info/verification.html
> 
> You can install binary package for specific version of python using pip
> For example do this on linux for python 3.8
>>> pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
> 
> You can build and install package from source using this command:
>>> pip install pyignite-0.5.2.tar.gz
> You can build wheel on your platform using this command:
>>> pip wheel --no-deps pyignite-0.5.2.tar.gz
> 
> For building C module, you should have python headers and C compiler
> installed.
> (i.e. for ubuntu sudo apt install build-essential python3-dev)
> In Mac OS X xcode-tools and python from homebrew are the best option.
> 
> In order to check whether C module works, use following:
>>> from pyignite import _cutils
>>> print(_cutils.hashcode('test'))
>>> 3556498
> 
> You can find documentation here:
> 
 
>> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
> 
> You can find examples here (to check them, you should start ignite
> locally):
> 
> 
 
>> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html
> Also, examples can be found in source archive in examples subfolder.
> docker-compose.yml is supplied in order to start ignite quickly. (Use
> `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> down` to shut down it)
> 
> Release notes:
> 
> 
 
>> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76
> 
> Git release tag was created:
> 
> 
 
>> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0
> 
> The vote is formal, see voting guidelines
> https://www.apache.org/foundation/voting.html
> 
> +1 - to accept pyignite-0.5.2-rc0
> 0 - don't care either way
> -1 - DO NOT accept pyignite-0.5.2-rc0
> 
> The vote finishes at 09/15/2021 15:00 UTC
> 
 
 
 --
 Sincerely yours, Ivan Daschinskiy
 
>> 

Re: [VOTE] Release pyignite 0.5.2-rc0

[Maxim Muzafarov]

+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
> > > Отправлено с 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 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. Building wheels from source -- passed
> > > >> 3. Installing wheels -- passed
> > > >>
> > > >> Checked on each steps C module and examples. -- passed
> > > >>
> > > >> Checked hashsums and gpg signatures -- passed
> > > >>
> > > >> пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :
> > > >>
> > > >>> 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 the link above, you will find source packages (*.tar.gz
> > > and
> > > >>> *.zip)
> > > >>> and binary packages (wheels) for windows (amd64) and linux (x86_64)
> > > >>> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg
> > signatures.
> > > >>> Code signing keys can be found here --
> > > >>> https://downloads.apache.org/ignite/KEYS
> > > >>> Here you can find instructions how to verify packages
> > > >>> https://www.apache.org/info/verification.html
> > > >>>
> > > >>> You can install binary package for specific version of python using
> > pip
> > > >>> For example do this on linux for python 3.8
> > > > pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
> > > >>>
> > > >>> You can build and install package from source using this command:
> > > > pip install pyignite-0.5.2.tar.gz
> > > >>> You can build wheel on your platform using this command:
> > > > pip wheel --no-deps pyignite-0.5.2.tar.gz
> > > >>>
> > > >>> For building C module, you should have python headers and C compiler
> > > >>> installed.
> > > >>> (i.e. for ubuntu sudo apt install build-essential python3-dev)
> > > >>> In Mac OS X xcode-tools and python from homebrew are the best option.
> > > >>>
> > > >>> In order to check whether C module works, use following:
> > > > from pyignite import _cutils
> > > > print(_cutils.hashcode('test'))
> > > > 3556498
> > > >>>
> > > >>> You can find documentation here:
> > > >>>
> > > >>
> > >
> > https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
> > > >>>
> > > >>> You can find examples here (to check them, you should start ignite
> > > >>> locally):
> > > >>>
> > > >>>
> > > >>
> > >
> > https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html
> > > >>> Also, examples can be found in source archive in examples subfolder.
> > > >>> docker-compose.yml is supplied in order to start ignite quickly. (Use
> > > >>> `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> > > >>> down` to shut down it)
> > > >>>
> > > >>> Release notes:
> > > >>>
> > > >>>
> > > >>
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76
> > > >>>
> > > >>> Git release tag was created:
> > > >>>
> > > >>>
> > > >>
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0
> > > >>>
> > > >>> The vote is formal, see voting guidelines
> > > >>> https://www.apache.org/foundation/voting.html
> > > >>>
> > > >>> +1 - to accept pyignite-0.5.2-rc0
> > > >>> 0 - don't care either way
> > > >>> -1 - DO NOT accept pyignite-0.5.2-rc0
> > > >>>
> > > >>> The vote finishes at 09/15/2021 15:00 UTC
> > > >>>
> > > >>
> > > >>
> > > >> --
> > > >> Sincerely yours, Ivan Daschinskiy
> > > >>
> > >
> >

Re[2]: Deprecating LOCAL cache

[Zhenya Stanilovsky]

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-cookies/
 
 
>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 of frustration.
>
>It is much more safe to ban a creation of LOCAL caches from thin clients.
>
>But it can survive for a while for ignite cluster nodes, client and server.
>
>вт, 14 сент. 2021 г. в 14:06, Maxim Muzafarov < mmu...@apache.org >:
> 
>> 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 Daschinsky < ivanda...@gmail.com >
>> wrote:
>> >
>> > 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 not
>> > PARTITIONED, so inconsistent behaviour from the beginning.
>> >
>> > So I suppose we should ban creation of LOCAL caches from thin client in
>> > 2.12 (fail attempt to create such caches in ClientRequestHandler
>> >
>> > вт, 14 сент. 2021 г. в 11:31, Ivan Daschinsky < ivanda...@gmail.com >:
>> >
>> > > >> 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 clients are released separately. I suppose that it is
>> better to
>> > > remove this feature from pyignite a little bit earlier.
>> > >
>> > > вт, 14 сент. 2021 г. в 11:21, Anton Vinogradov < a...@apache.org >:
>> > >
>> > >> > 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, Sep 14, 2021 at 10:30 AM Ivan Daschinsky < ivanda...@gmail.com
>> >
>> > >> wrote:
>> > >>
>> > >> > >> 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) before 2.13 release?
>> > >> >
>> > >> > вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov < nizhi...@apache.org
>> >:
>> > >> >
>> > >> > > 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 < ivanda...@gmail.com
>> >
>> > >> > > написал(а):
>> > >> > > >
>> > >> > > > I personally support deprecation, but we should at least have a
>> > >> plan.
>> > >> > > > I suppose that putting annotations and removing documentation
>> are
>> > >> not
>> > >> > > > enough.
>> > >> > > >
>> > >> > > >
>> > >> > > > пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov <
>>  mmu...@apache.org >:
>> > >> > > >
>> > >> > > >> Ivan,
>> > >> > > >>
>> > >> > > >> I don't think we can remove LOCAL caches at the nearest time,
>> so
>> > >> there
>> > >> > > >> is no plan for that. I can only imagine a single release that
>> will
>> > >> > > >> contain all the breaking changes we want to apply in 2.x
>> version.
>> > >> > > >>
>> > >> > > >> My point here is only about deprecation:
>> > >> > > >> - there are a lot of motivation points to remove written in
>> this
>> > >> > thread;
>> > >> > > >> - I always hear from the support team that they do not
>> recommend
>> > >> using
>> > >> > > >> local caches;
>> > >> > > >> - I haven't seen any bugs fixed for a long time for local
>> caches
>> > >> > > >> (suppose that we are not maintaining them);
>> > >> > > >>
>> > >> > > >> I just want to make sure that all these points are reflected
>> in the
>> > >> > > >> code base, so propose to mark them as deprecated.
>> > >> > > >>
>> > >> > > >> On Mon, 13 

Re: Deprecating LOCAL cache

[Pavel Tupitsyn]

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 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 of frustration.
>
> It is much more safe to ban a creation of LOCAL caches from thin clients.
>
> But it can survive for a while for ignite cluster nodes, client and server.
>
> вт, 14 сент. 2021 г. в 14:06, Maxim Muzafarov :
>
> > 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 Daschinsky 
> > wrote:
> > >
> > > 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 not
> > > PARTITIONED, so inconsistent behaviour from the beginning.
> > >
> > > So I suppose we should ban creation of LOCAL caches from thin client in
> > > 2.12 (fail attempt to create such caches in ClientRequestHandler
> > >
> > > вт, 14 сент. 2021 г. в 11:31, Ivan Daschinsky :
> > >
> > > > >> 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 clients are released separately. I suppose that it is
> > better to
> > > > remove this feature from pyignite a little bit earlier.
> > > >
> > > > вт, 14 сент. 2021 г. в 11:21, Anton Vinogradov :
> > > >
> > > >> > 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, Sep 14, 2021 at 10:30 AM Ivan Daschinsky <
> ivanda...@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >> > >> 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) before 2.13 release?
> > > >> >
> > > >> > вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov <
> nizhi...@apache.org
> > >:
> > > >> >
> > > >> > > 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 <
> ivanda...@gmail.com
> > >
> > > >> > > написал(а):
> > > >> > > >
> > > >> > > > I personally support deprecation, but we should at least have
> a
> > > >> plan.
> > > >> > > > I suppose that putting annotations and removing documentation
> > are
> > > >> not
> > > >> > > > enough.
> > > >> > > >
> > > >> > > >
> > > >> > > > пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov <
> > mmu...@apache.org>:
> > > >> > > >
> > > >> > > >> Ivan,
> > > >> > > >>
> > > >> > > >> I don't think we can remove LOCAL caches at the nearest time,
> > so
> > > >> there
> > > >> > > >> is no plan for that. I can only imagine a single release that
> > will
> > > >> > > >> contain all the breaking changes we want to apply in 2.x
> > version.
> > > >> > > >>
> > > >> > > >> My point here is only about deprecation:
> > > >> > > >> - there are a lot of motivation points to remove written in
> > this
> > > >> > thread;
> > > >> > > >> - I always hear from the support team that they do not
> > recommend
> > > >> using
> > > >> > > >> local caches;
> > > >> > > >> - I haven't seen any bugs fixed for a long time for local
> > caches
> > > >> > > >> (suppose that we are not maintaining them);
> > > >> > > >>
> > > >> > > >> I just want to make sure that all these points are reflected
> > in the
> > > >> > > >> code base, so propose to mark them as deprecated.
> > > >> > > >>
> > > >> > > >> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky <
> > > >> ivanda...@gmail.com>
> > > >> > > >> wrote:
> > 

Re: Deprecating LOCAL cache

[Ivan Daschinsky]

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 of frustration.

It is much more safe to ban a creation of LOCAL caches from thin clients.

But it can survive for a while for ignite cluster nodes, client and server.

вт, 14 сент. 2021 г. в 14:06, Maxim Muzafarov :

> 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 Daschinsky 
> wrote:
> >
> > 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 not
> > PARTITIONED, so inconsistent behaviour from the beginning.
> >
> > So I suppose we should ban creation of LOCAL caches from thin client in
> > 2.12 (fail attempt to create such caches in ClientRequestHandler
> >
> > вт, 14 сент. 2021 г. в 11:31, Ivan Daschinsky :
> >
> > > >> 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 clients are released separately. I suppose that it is
> better to
> > > remove this feature from pyignite a little bit earlier.
> > >
> > > вт, 14 сент. 2021 г. в 11:21, Anton Vinogradov :
> > >
> > >> > 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, Sep 14, 2021 at 10:30 AM Ivan Daschinsky  >
> > >> wrote:
> > >>
> > >> > >> 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) before 2.13 release?
> > >> >
> > >> > вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov  >:
> > >> >
> > >> > > 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 and removing documentation
> are
> > >> not
> > >> > > > enough.
> > >> > > >
> > >> > > >
> > >> > > > пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov <
> mmu...@apache.org>:
> > >> > > >
> > >> > > >> Ivan,
> > >> > > >>
> > >> > > >> I don't think we can remove LOCAL caches at the nearest time,
> so
> > >> there
> > >> > > >> is no plan for that. I can only imagine a single release that
> will
> > >> > > >> contain all the breaking changes we want to apply in 2.x
> version.
> > >> > > >>
> > >> > > >> My point here is only about deprecation:
> > >> > > >> - there are a lot of motivation points to remove written in
> this
> > >> > thread;
> > >> > > >> - I always hear from the support team that they do not
> recommend
> > >> using
> > >> > > >> local caches;
> > >> > > >> - I haven't seen any bugs fixed for a long time for local
> caches
> > >> > > >> (suppose that we are not maintaining them);
> > >> > > >>
> > >> > > >> I just want to make sure that all these points are reflected
> in the
> > >> > > >> code base, so propose to mark them as deprecated.
> > >> > > >>
> > >> > > >> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky <
> > >> ivanda...@gmail.com>
> > >> > > >> wrote:
> > >> > > >>>
> > >> > > >>> Hi, Maxim. And what is the plan of removing this
> functionality?
> > >> And I
> > >> > > >> also
> > >> > > >>> have some questions regarding deprecation in binary protocol
> > >> > > >>>
> > >> > > >>> Currently thin client binary protocol
> > >> > > >>> 1. Does support LOCAL caches
> > >> > > >>> 2. Does not support node filters.
> > >> > > >>>
> > >> > > >>> I can hardly imagine the usefulness of this feature on thin
> > >> clients,
> > >> > > >>> especially with 

Re: Deprecating LOCAL cache

[Maxim Muzafarov]

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 Daschinsky  wrote:
>
> 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 not
> PARTITIONED, so inconsistent behaviour from the beginning.
>
> So I suppose we should ban creation of LOCAL caches from thin client in
> 2.12 (fail attempt to create such caches in ClientRequestHandler
>
> вт, 14 сент. 2021 г. в 11:31, Ivan Daschinsky :
>
> > >> 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 clients are released separately. I suppose that it is better to
> > remove this feature from pyignite a little bit earlier.
> >
> > вт, 14 сент. 2021 г. в 11:21, Anton Vinogradov :
> >
> >> > 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, Sep 14, 2021 at 10:30 AM Ivan Daschinsky 
> >> wrote:
> >>
> >> > >> 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) before 2.13 release?
> >> >
> >> > вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov :
> >> >
> >> > > 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 and removing documentation are
> >> not
> >> > > > enough.
> >> > > >
> >> > > >
> >> > > > пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov :
> >> > > >
> >> > > >> Ivan,
> >> > > >>
> >> > > >> I don't think we can remove LOCAL caches at the nearest time, so
> >> there
> >> > > >> is no plan for that. I can only imagine a single release that will
> >> > > >> contain all the breaking changes we want to apply in 2.x version.
> >> > > >>
> >> > > >> My point here is only about deprecation:
> >> > > >> - there are a lot of motivation points to remove written in this
> >> > thread;
> >> > > >> - I always hear from the support team that they do not recommend
> >> using
> >> > > >> local caches;
> >> > > >> - I haven't seen any bugs fixed for a long time for local caches
> >> > > >> (suppose that we are not maintaining them);
> >> > > >>
> >> > > >> I just want to make sure that all these points are reflected in the
> >> > > >> code base, so propose to mark them as deprecated.
> >> > > >>
> >> > > >> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky <
> >> ivanda...@gmail.com>
> >> > > >> wrote:
> >> > > >>>
> >> > > >>> Hi, Maxim. And what is the plan of removing this functionality?
> >> And I
> >> > > >> also
> >> > > >>> have some questions regarding deprecation in binary protocol
> >> > > >>>
> >> > > >>> Currently thin client binary protocol
> >> > > >>> 1. Does support LOCAL caches
> >> > > >>> 2. Does not support node filters.
> >> > > >>>
> >> > > >>> I can hardly imagine the usefulness of this feature on thin
> >> clients,
> >> > > >>> especially with partition awareness, but nevertheless.
> >> > > >>> What is expected behaviour if this feature is removed from newest
> >> > > version
> >> > > >>> of Apache Ignite server and and and old client is requesting
> >> > > >>> creation of LOCAL cache?
> >> > > >>>
> >> > > >>> вс, 12 сент. 2021 г. в 15:10, Maxim Muzafarov  >> >:
> >> > > >>>
> >> > >  Folks,
> >> > > 
> >> > >  Let's get back to the discussion of obsolete LOCAL caches since a
> >> > lot
> >> > >  of time has passed since the last discussion.
> >> > >  I've created an issue [1] for deprecation. Let's deprecate them
> >> at
> >> > >  least at the next 2.12 release.
> >> > > 
> >> > >  WDYT?
> >> > > 
> >> > > 
> >> > >  [1] https://issues.apache.org/jira/browse/IGNITE-15499
> 

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[Maxim Muzafarov]

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 Tupitsyn  wrote:
>
> 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 with duplicate binaries, I've created another ticket [2]
>
>
> > Why do we still ship Apache.Ignite.exe if it does not run?
> It runs on Windows. For Linux we ship Apache.Ignite.dll.
>
>
> I don't think any of this is a blocker for the current release.
> - Out-of-support SDK only affects those who build from source, and it went
> out of support only recently
> - Duplicate binaries are there for a long time and no one was complaining
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15504
> [2] https://issues.apache.org/jira/browse/IGNITE-15505
>
> On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev 
> wrote:
>
> > 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' was not found.
> >
> >
> >  - The following frameworks were found:
> >
> >
> >  5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App]
> >
> >
> > You can resolve the problem by installing the specified framework and/or
> > SDK.
> >
> >
> > The specified framework can be found at:
> >
> >
> >  -
> >
> > https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App_version=2.0.0=x64=ubuntu.21.04-x64
> >
> > When I have also installed 3.1 and 2.0, now I see:
> >
> > The active test run was aborted. Reason: Test host process crashed : No
> > usable version of the libssl was found
> >
> > It looks like we have to bump the permitted .NET version.
> >
> > From the slim binary package I also can't run .NET:
> >
> > ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0%
> > dotnet Apache.Ignite.dll
> > Error:
> >  An assembly specified in the application dependencies manifest
> > (Apache.Ignite.deps.json) was not found:
> >package: 'System.Configuration.ConfigurationManager', version: '4.4.0'
> >path: 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll'
> >
> > Do we have any instructions on how to run it under Linux? Why do we still
> > ship Apache.Ignite.exe if it does not run?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>:
> >
> > > 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 two issue be merged into the ignite-2.11 branch?
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-14404
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-15503
> > > >>
> > > >> 在 2021/9/13 17:12, Pavel Tupitsyn 写道:
> > > >>> +1
> > > >>>
> > > >>> Downloaded binary packages, started a cluster with a few nodes,
> > tested
> > > >> new
> > > >>> .NET examples.
> > > >>>
> > > >>> On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
> > > >>>wrote:
> > > >>>
> > >  Thanks Maxim !
> > >  I tries to compare this ver with 2.10 (some performance tests with
> > >  persistence and transactional\atomic payload) and seems all ok
> > there.
> > >  +1 from me.
> > > 
> > > > Dear Community,
> > > >
> > > >
> > > > The release candidate for the 2.11 version is ready.
> > > >
> > > >
> > > > I have uploaded a release candidate to:
> > > > https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
> > > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/
> > > >
> > > > The following staging can be used for testing:
> > > >
> > > >>
> > > https://repository.apache.org/content/repositories/orgapacheignite-1526/
> > > >>
> > >
> > https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
> > > > Tag name is 2.11.0-rc2:
> > > >
> > > >>
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2
> > > > RELEASE_NOTES:
> > > >
> > > >>
> > >
> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11
> > > > Complete list of resolved issues:
> > > >

Re: [VOTE] Release pyignite 0.5.2-rc0

[Ivan Daschinsky]

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:
>
> > +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_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. -- passed
> > >>
> > >> Checked hashsums and gpg signatures -- passed
> > >>
> > >> пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :
> > >>
> > >>> 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 the link above, you will find source packages (*.tar.gz
> > and
> > >>> *.zip)
> > >>> and binary packages (wheels) for windows (amd64) and linux (x86_64)
> > >>> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg
> signatures.
> > >>> Code signing keys can be found here --
> > >>> https://downloads.apache.org/ignite/KEYS
> > >>> Here you can find instructions how to verify packages
> > >>> https://www.apache.org/info/verification.html
> > >>>
> > >>> You can install binary package for specific version of python using
> pip
> > >>> For example do this on linux for python 3.8
> > > pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
> > >>>
> > >>> You can build and install package from source using this command:
> > > pip install pyignite-0.5.2.tar.gz
> > >>> You can build wheel on your platform using this command:
> > > pip wheel --no-deps pyignite-0.5.2.tar.gz
> > >>>
> > >>> For building C module, you should have python headers and C compiler
> > >>> installed.
> > >>> (i.e. for ubuntu sudo apt install build-essential python3-dev)
> > >>> In Mac OS X xcode-tools and python from homebrew are the best option.
> > >>>
> > >>> In order to check whether C module works, use following:
> > > from pyignite import _cutils
> > > print(_cutils.hashcode('test'))
> > > 3556498
> > >>>
> > >>> You can find documentation here:
> > >>>
> > >>
> >
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
> > >>>
> > >>> You can find examples here (to check them, you should start ignite
> > >>> locally):
> > >>>
> > >>>
> > >>
> >
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html
> > >>> Also, examples can be found in source archive in examples subfolder.
> > >>> docker-compose.yml is supplied in order to start ignite quickly. (Use
> > >>> `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> > >>> down` to shut down it)
> > >>>
> > >>> Release notes:
> > >>>
> > >>>
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76
> > >>>
> > >>> Git release tag was created:
> > >>>
> > >>>
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0
> > >>>
> > >>> The vote is formal, see voting guidelines
> > >>> https://www.apache.org/foundation/voting.html
> > >>>
> > >>> +1 - to accept pyignite-0.5.2-rc0
> > >>> 0 - don't care either way
> > >>> -1 - DO NOT accept pyignite-0.5.2-rc0
> > >>>
> > >>> The vote finishes at 09/15/2021 15:00 UTC
> > >>>
> > >>
> > >>
> > >> --
> > >> Sincerely yours, Ivan Daschinskiy
> > >>
> >
>

Re: [VOTE] Release pyignite 0.5.2-rc0

[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:

> +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_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. -- passed
> >>
> >> Checked hashsums and gpg signatures -- passed
> >>
> >> пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :
> >>
> >>> 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 the link above, you will find source packages (*.tar.gz
> and
> >>> *.zip)
> >>> and binary packages (wheels) for windows (amd64) and linux (x86_64)
> >>> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.
> >>> Code signing keys can be found here --
> >>> https://downloads.apache.org/ignite/KEYS
> >>> Here you can find instructions how to verify packages
> >>> https://www.apache.org/info/verification.html
> >>>
> >>> You can install binary package for specific version of python using pip
> >>> For example do this on linux for python 3.8
> > pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
> >>>
> >>> You can build and install package from source using this command:
> > pip install pyignite-0.5.2.tar.gz
> >>> You can build wheel on your platform using this command:
> > pip wheel --no-deps pyignite-0.5.2.tar.gz
> >>>
> >>> For building C module, you should have python headers and C compiler
> >>> installed.
> >>> (i.e. for ubuntu sudo apt install build-essential python3-dev)
> >>> In Mac OS X xcode-tools and python from homebrew are the best option.
> >>>
> >>> In order to check whether C module works, use following:
> > from pyignite import _cutils
> > print(_cutils.hashcode('test'))
> > 3556498
> >>>
> >>> You can find documentation here:
> >>>
> >>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
> >>>
> >>> You can find examples here (to check them, you should start ignite
> >>> locally):
> >>>
> >>>
> >>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html
> >>> Also, examples can be found in source archive in examples subfolder.
> >>> docker-compose.yml is supplied in order to start ignite quickly. (Use
> >>> `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> >>> down` to shut down it)
> >>>
> >>> Release notes:
> >>>
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76
> >>>
> >>> Git release tag was created:
> >>>
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0
> >>>
> >>> The vote is formal, see voting guidelines
> >>> https://www.apache.org/foundation/voting.html
> >>>
> >>> +1 - to accept pyignite-0.5.2-rc0
> >>> 0 - don't care either way
> >>> -1 - DO NOT accept pyignite-0.5.2-rc0
> >>>
> >>> The vote finishes at 09/15/2021 15:00 UTC
> >>>
> >>
> >>
> >> --
> >> Sincerely yours, Ivan Daschinskiy
> >>
>

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[Pavel Tupitsyn]

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 with duplicate binaries, I've created another ticket [2]


> Why do we still ship Apache.Ignite.exe if it does not run?
It runs on Windows. For Linux we ship Apache.Ignite.dll.


I don't think any of this is a blocker for the current release.
- Out-of-support SDK only affects those who build from source, and it went
out of support only recently
- Duplicate binaries are there for a long time and no one was complaining


[1] https://issues.apache.org/jira/browse/IGNITE-15504
[2] https://issues.apache.org/jira/browse/IGNITE-15505

On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev 
wrote:

> 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' was not found.
>
>
>  - The following frameworks were found:
>
>
>  5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App]
>
>
> You can resolve the problem by installing the specified framework and/or
> SDK.
>
>
> The specified framework can be found at:
>
>
>  -
>
> https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App_version=2.0.0=x64=ubuntu.21.04-x64
>
> When I have also installed 3.1 and 2.0, now I see:
>
> The active test run was aborted. Reason: Test host process crashed : No
> usable version of the libssl was found
>
> It looks like we have to bump the permitted .NET version.
>
> From the slim binary package I also can't run .NET:
>
> ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0%
> dotnet Apache.Ignite.dll
> Error:
>  An assembly specified in the application dependencies manifest
> (Apache.Ignite.deps.json) was not found:
>package: 'System.Configuration.ConfigurationManager', version: '4.4.0'
>path: 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll'
>
> Do we have any instructions on how to run it under Linux? Why do we still
> ship Apache.Ignite.exe if it does not run?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>:
>
> > 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 two issue be merged into the ignite-2.11 branch?
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-14404
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-15503
> > >>
> > >> 在 2021/9/13 17:12, Pavel Tupitsyn 写道:
> > >>> +1
> > >>>
> > >>> Downloaded binary packages, started a cluster with a few nodes,
> tested
> > >> new
> > >>> .NET examples.
> > >>>
> > >>> On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
> > >>>wrote:
> > >>>
> >  Thanks Maxim !
> >  I tries to compare this ver with 2.10 (some performance tests with
> >  persistence and transactional\atomic payload) and seems all ok
> there.
> >  +1 from me.
> > 
> > > Dear Community,
> > >
> > >
> > > The release candidate for the 2.11 version is ready.
> > >
> > >
> > > I have uploaded a release candidate to:
> > > https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
> > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/
> > >
> > > The following staging can be used for testing:
> > >
> > >>
> > https://repository.apache.org/content/repositories/orgapacheignite-1526/
> > >>
> >
> https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
> > > Tag name is 2.11.0-rc2:
> > >
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2
> > > RELEASE_NOTES:
> > >
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11
> > > Complete list of resolved issues:
> > >
> > >>
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11%27
> >  ))
> > > DEVNOTES:
> > >
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.11
> > > Additional checks have been performed (available for users included
> > >> into
> > > the release group on TeamCity).
> > >
> > > TC [Check RC: Licenses, compile, chksum]
> > >
> > >>
> >
> 

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[Shishkov Ilya]

> 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 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' was not found.
>
>
>  - The following frameworks were found:
>
>
>  5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App]
>
>
> You can resolve the problem by installing the specified framework and/or
> SDK.
>
>
> The specified framework can be found at:
>
>
>  -
>
> https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App_version=2.0.0=x64=ubuntu.21.04-x64
>
> When I have also installed 3.1 and 2.0, now I see:
>
> The active test run was aborted. Reason: Test host process crashed : No
> usable version of the libssl was found
>
> It looks like we have to bump the permitted .NET version.
>
> From the slim binary package I also can't run .NET:
>
> ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0%
> dotnet Apache.Ignite.dll
> Error:
>  An assembly specified in the application dependencies manifest
> (Apache.Ignite.deps.json) was not found:
>package: 'System.Configuration.ConfigurationManager', version: '4.4.0'
>path: 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll'
>
> Do we have any instructions on how to run it under Linux? Why do we still
> ship Apache.Ignite.exe if it does not run?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>:
>
> > 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 two issue be merged into the ignite-2.11 branch?
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-14404
> > >>
> > >> https://issues.apache.org/jira/browse/IGNITE-15503
> > >>
> > >> 在 2021/9/13 17:12, Pavel Tupitsyn 写道:
> > >>> +1
> > >>>
> > >>> Downloaded binary packages, started a cluster with a few nodes,
> tested
> > >> new
> > >>> .NET examples.
> > >>>
> > >>> On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
> > >>>wrote:
> > >>>
> >  Thanks Maxim !
> >  I tries to compare this ver with 2.10 (some performance tests with
> >  persistence and transactional\atomic payload) and seems all ok
> there.
> >  +1 from me.
> > 
> > > Dear Community,
> > >
> > >
> > > The release candidate for the 2.11 version is ready.
> > >
> > >
> > > I have uploaded a release candidate to:
> > > https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
> > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/
> > >
> > > The following staging can be used for testing:
> > >
> > >>
> > https://repository.apache.org/content/repositories/orgapacheignite-1526/
> > >>
> >
> https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
> > > Tag name is 2.11.0-rc2:
> > >
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2
> > > RELEASE_NOTES:
> > >
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11
> > > Complete list of resolved issues:
> > >
> > >>
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11%27
> >  ))
> > > DEVNOTES:
> > >
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.11
> > > Additional checks have been performed (available for users included
> > >> into
> > > the release group on TeamCity).
> > >
> > > TC [Check RC: Licenses, compile, chksum]
> > >
> > >>
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=6176219=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=buildResultsDiv
> > > The vote is formal, see voting guidelines
> > > https://www.apache.org/foundation/voting.html
> > >
> > > +1 - to accept Apache Ignite 2.11.0-rc2
> > > 0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite Ignite 2.11.0-rc2 (explain why)
> > >
> > > See notes on how to verify release here
> > > https://www.apache.org/info/verification.html
> > > and
> > >
> > >>
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> > > This vote will be open for 4 days until Thu Sep 16, 12:00 2021
> > 

Re: [VOTE] Release pyignite 0.5.2-rc0

[Shishkov Ilya]

+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, 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. Building wheels from source -- passed
> >> 3. Installing wheels -- passed
> >>
> >> Checked on each steps C module and examples. -- passed
> >>
> >> Checked hashsums and gpg signatures -- passed
> >>
> >> пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :
> >>
> >>> 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 the link above, you will find source packages (*.tar.gz
> and
> >>> *.zip)
> >>> and binary packages (wheels) for windows (amd64) and linux (x86_64)
> >>> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.
> >>> Code signing keys can be found here --
> >>> https://downloads.apache.org/ignite/KEYS
> >>> Here you can find instructions how to verify packages
> >>> https://www.apache.org/info/verification.html
> >>>
> >>> You can install binary package for specific version of python using pip
> >>> For example do this on linux for python 3.8
> > pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
> >>>
> >>> You can build and install package from source using this command:
> > pip install pyignite-0.5.2.tar.gz
> >>> You can build wheel on your platform using this command:
> > pip wheel --no-deps pyignite-0.5.2.tar.gz
> >>>
> >>> For building C module, you should have python headers and C compiler
> >>> installed.
> >>> (i.e. for ubuntu sudo apt install build-essential python3-dev)
> >>> In Mac OS X xcode-tools and python from homebrew are the best option.
> >>>
> >>> In order to check whether C module works, use following:
> > from pyignite import _cutils
> > print(_cutils.hashcode('test'))
> > 3556498
> >>>
> >>> You can find documentation here:
> >>>
> >>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
> >>>
> >>> You can find examples here (to check them, you should start ignite
> >>> locally):
> >>>
> >>>
> >>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html
> >>> Also, examples can be found in source archive in examples subfolder.
> >>> docker-compose.yml is supplied in order to start ignite quickly. (Use
> >>> `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> >>> down` to shut down it)
> >>>
> >>> Release notes:
> >>>
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76
> >>>
> >>> Git release tag was created:
> >>>
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0
> >>>
> >>> The vote is formal, see voting guidelines
> >>> https://www.apache.org/foundation/voting.html
> >>>
> >>> +1 - to accept pyignite-0.5.2-rc0
> >>> 0 - don't care either way
> >>> -1 - DO NOT accept pyignite-0.5.2-rc0
> >>>
> >>> The vote finishes at 09/15/2021 15:00 UTC
> >>>
> >>
> >>
> >> --
> >> Sincerely yours, Ivan Daschinskiy
> >>
>

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_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. -- passed
>> 
>> Checked hashsums and gpg signatures -- passed
>> 
>> пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :
>> 
>>> 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 the link above, you will find source packages (*.tar.gz and
>>> *.zip)
>>> and binary packages (wheels) for windows (amd64) and linux (x86_64)
>>> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.
>>> Code signing keys can be found here --
>>> https://downloads.apache.org/ignite/KEYS
>>> Here you can find instructions how to verify packages
>>> https://www.apache.org/info/verification.html
>>> 
>>> You can install binary package for specific version of python using pip
>>> For example do this on linux for python 3.8
> pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
>>> 
>>> You can build and install package from source using this command:
> pip install pyignite-0.5.2.tar.gz
>>> You can build wheel on your platform using this command:
> pip wheel --no-deps pyignite-0.5.2.tar.gz
>>> 
>>> For building C module, you should have python headers and C compiler
>>> installed.
>>> (i.e. for ubuntu sudo apt install build-essential python3-dev)
>>> In Mac OS X xcode-tools and python from homebrew are the best option.
>>> 
>>> In order to check whether C module works, use following:
> from pyignite import _cutils
> print(_cutils.hashcode('test'))
> 3556498
>>> 
>>> You can find documentation here:
>>> 
>> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
>>> 
>>> You can find examples here (to check them, you should start ignite
>>> locally):
>>> 
>>> 
>> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html
>>> Also, examples can be found in source archive in examples subfolder.
>>> docker-compose.yml is supplied in order to start ignite quickly. (Use
>>> `docker-compose up -d` to start 3 nodes cluster and `docker-compose
>>> down` to shut down it)
>>> 
>>> Release notes:
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76
>>> 
>>> Git release tag was created:
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0
>>> 
>>> The vote is formal, see voting guidelines
>>> https://www.apache.org/foundation/voting.html
>>> 
>>> +1 - to accept pyignite-0.5.2-rc0
>>> 0 - don't care either way
>>> -1 - DO NOT accept pyignite-0.5.2-rc0
>>> 
>>> The vote finishes at 09/15/2021 15:00 UTC
>>> 
>> 
>> 
>> --
>> Sincerely yours, Ivan Daschinskiy
>> 

Re: Deprecating LOCAL cache

[Ivan Daschinsky]

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 not
PARTITIONED, so inconsistent behaviour from the beginning.

So I suppose we should ban creation of LOCAL caches from thin client in
2.12 (fail attempt to create such caches in ClientRequestHandler

вт, 14 сент. 2021 г. в 11:31, Ivan Daschinsky :

> >> 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 clients are released separately. I suppose that it is better to
> remove this feature from pyignite a little bit earlier.
>
> вт, 14 сент. 2021 г. в 11:21, Anton Vinogradov :
>
>> > 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, Sep 14, 2021 at 10:30 AM Ivan Daschinsky 
>> wrote:
>>
>> > >> 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) before 2.13 release?
>> >
>> > вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov :
>> >
>> > > 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 and removing documentation are
>> not
>> > > > enough.
>> > > >
>> > > >
>> > > > пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov :
>> > > >
>> > > >> Ivan,
>> > > >>
>> > > >> I don't think we can remove LOCAL caches at the nearest time, so
>> there
>> > > >> is no plan for that. I can only imagine a single release that will
>> > > >> contain all the breaking changes we want to apply in 2.x version.
>> > > >>
>> > > >> My point here is only about deprecation:
>> > > >> - there are a lot of motivation points to remove written in this
>> > thread;
>> > > >> - I always hear from the support team that they do not recommend
>> using
>> > > >> local caches;
>> > > >> - I haven't seen any bugs fixed for a long time for local caches
>> > > >> (suppose that we are not maintaining them);
>> > > >>
>> > > >> I just want to make sure that all these points are reflected in the
>> > > >> code base, so propose to mark them as deprecated.
>> > > >>
>> > > >> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky <
>> ivanda...@gmail.com>
>> > > >> wrote:
>> > > >>>
>> > > >>> Hi, Maxim. And what is the plan of removing this functionality?
>> And I
>> > > >> also
>> > > >>> have some questions regarding deprecation in binary protocol
>> > > >>>
>> > > >>> Currently thin client binary protocol
>> > > >>> 1. Does support LOCAL caches
>> > > >>> 2. Does not support node filters.
>> > > >>>
>> > > >>> I can hardly imagine the usefulness of this feature on thin
>> clients,
>> > > >>> especially with partition awareness, but nevertheless.
>> > > >>> What is expected behaviour if this feature is removed from newest
>> > > version
>> > > >>> of Apache Ignite server and and and old client is requesting
>> > > >>> creation of LOCAL cache?
>> > > >>>
>> > > >>> вс, 12 сент. 2021 г. в 15:10, Maxim Muzafarov > >:
>> > > >>>
>> > >  Folks,
>> > > 
>> > >  Let's get back to the discussion of obsolete LOCAL caches since a
>> > lot
>> > >  of time has passed since the last discussion.
>> > >  I've created an issue [1] for deprecation. Let's deprecate them
>> at
>> > >  least at the next 2.12 release.
>> > > 
>> > >  WDYT?
>> > > 
>> > > 
>> > >  [1] https://issues.apache.org/jira/browse/IGNITE-15499
>> > > 
>> > >  On Fri, 27 Jul 2018 at 20:59, Valentin Kulichenko
>> > >   wrote:
>> > > >
>> > > > Guys,
>> > > >
>> > > > Use cases for local caches are rare, but they definitely exist.
>> I
>> > > >> don't
>> > > > think it's a very good idea to deprecate this functionality at
>> this
>> > >  point.
>> > > >
>> > > > At the same point, it's obviously not the most critical part of
>> the
>> > > > product, so maintaining the whole separate implementation for
>> it is
>> > > > probably an overkill. 

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[Ilya Kasnacheev]

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' was not found.


 - The following frameworks were found:


 5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App]


You can resolve the problem by installing the specified framework and/or
SDK.


The specified framework can be found at:


 -
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App_version=2.0.0=x64=ubuntu.21.04-x64

When I have also installed 3.1 and 2.0, now I see:

The active test run was aborted. Reason: Test host process crashed : No
usable version of the libssl was found

It looks like we have to bump the permitted .NET version.

>From the slim binary package I also can't run .NET:

~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0%
dotnet Apache.Ignite.dll
Error:
 An assembly specified in the application dependencies manifest
(Apache.Ignite.deps.json) was not found:
   package: 'System.Configuration.ConfigurationManager', version: '4.4.0'
   path: 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll'

Do we have any instructions on how to run it under Linux? Why do we still
ship Apache.Ignite.exe if it does not run?

Regards,
-- 
Ilya Kasnacheev


вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>:

> 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 two issue be merged into the ignite-2.11 branch?
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-14404
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-15503
> >>
> >> 在 2021/9/13 17:12, Pavel Tupitsyn 写道:
> >>> +1
> >>>
> >>> Downloaded binary packages, started a cluster with a few nodes, tested
> >> new
> >>> .NET examples.
> >>>
> >>> On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
> >>>wrote:
> >>>
>  Thanks Maxim !
>  I tries to compare this ver with 2.10 (some performance tests with
>  persistence and transactional\atomic payload) and seems all ok there.
>  +1 from me.
> 
> > Dear Community,
> >
> >
> > The release candidate for the 2.11 version is ready.
> >
> >
> > I have uploaded a release candidate to:
> > https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
> > https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/
> >
> > The following staging can be used for testing:
> >
> >>
> https://repository.apache.org/content/repositories/orgapacheignite-1526/
> >>
> https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
> > Tag name is 2.11.0-rc2:
> >
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2
> > RELEASE_NOTES:
> >
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11
> > Complete list of resolved issues:
> >
> >>
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11%27
>  ))
> > DEVNOTES:
> >
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.11
> > Additional checks have been performed (available for users included
> >> into
> > the release group on TeamCity).
> >
> > TC [Check RC: Licenses, compile, chksum]
> >
> >>
> https://ci.ignite.apache.org/viewLog.html?buildId=6176219=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=buildResultsDiv
> > The vote is formal, see voting guidelines
> > https://www.apache.org/foundation/voting.html
> >
> > +1 - to accept Apache Ignite 2.11.0-rc2
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite Ignite 2.11.0-rc2 (explain why)
> >
> > See notes on how to verify release here
> > https://www.apache.org/info/verification.html
> > and
> >
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> > This vote will be open for 4 days until Thu Sep 16, 12:00 2021
> (Moscow
> > time).
> > Please, write me down the thread if you need additional time to check
> > the release.
> >
> >>
> https://www.timeanddate.com/countdown/vote?iso=20210916T12=166=%5BVOTE%5D+Release+Apache+Ignite+2.10.0+RC2=serif=1
> 
> 
> 

Re: [VOTE] Release pyignite 0.5.2-rc0

[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_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. -- passed
>
> Checked hashsums and gpg signatures -- passed
>
> пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :
>
> > 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 the link above, you will find source packages (*.tar.gz and
> > *.zip)
> > and binary packages (wheels) for windows (amd64) and linux (x86_64)
> > for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.
> > Code signing keys can be found here --
> > https://downloads.apache.org/ignite/KEYS
> > Here you can find instructions how to verify packages
> > https://www.apache.org/info/verification.html
> >
> > You can install binary package for specific version of python using pip
> > For example do this on linux for python 3.8
> > >> pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
> >
> > You can build and install package from source using this command:
> > >> pip install pyignite-0.5.2.tar.gz
> > You can build wheel on your platform using this command:
> > >> pip wheel --no-deps pyignite-0.5.2.tar.gz
> >
> > For building C module, you should have python headers and C compiler
> > installed.
> > (i.e. for ubuntu sudo apt install build-essential python3-dev)
> > In Mac OS X xcode-tools and python from homebrew are the best option.
> >
> > In order to check whether C module works, use following:
> > >> from pyignite import _cutils
> > >> print(_cutils.hashcode('test'))
> > >> 3556498
> >
> > You can find documentation here:
> >
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
> >
> > You can find examples here (to check them, you should start ignite
> > locally):
> >
> >
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html
> > Also, examples can be found in source archive in examples subfolder.
> > docker-compose.yml is supplied in order to start ignite quickly. (Use
> > `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> > down` to shut down it)
> >
> > Release notes:
> >
> >
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76
> >
> > Git release tag was created:
> >
> >
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0
> >
> > The vote is formal, see voting guidelines
> > https://www.apache.org/foundation/voting.html
> >
> > +1 - to accept pyignite-0.5.2-rc0
> > 0 - don't care either way
> > -1 - DO NOT accept pyignite-0.5.2-rc0
> >
> > The vote finishes at 09/15/2021 15:00 UTC
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

Re: Deprecating LOCAL cache

[Ivan Daschinsky]

>> 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 clients are released separately. I suppose that it is better to
remove this feature from pyignite a little bit earlier.

вт, 14 сент. 2021 г. в 11:21, Anton Vinogradov :

> > 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, Sep 14, 2021 at 10:30 AM Ivan Daschinsky 
> wrote:
>
> > >> 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) before 2.13 release?
> >
> > вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov :
> >
> > > 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 and removing documentation are not
> > > > enough.
> > > >
> > > >
> > > > пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov :
> > > >
> > > >> Ivan,
> > > >>
> > > >> I don't think we can remove LOCAL caches at the nearest time, so
> there
> > > >> is no plan for that. I can only imagine a single release that will
> > > >> contain all the breaking changes we want to apply in 2.x version.
> > > >>
> > > >> My point here is only about deprecation:
> > > >> - there are a lot of motivation points to remove written in this
> > thread;
> > > >> - I always hear from the support team that they do not recommend
> using
> > > >> local caches;
> > > >> - I haven't seen any bugs fixed for a long time for local caches
> > > >> (suppose that we are not maintaining them);
> > > >>
> > > >> I just want to make sure that all these points are reflected in the
> > > >> code base, so propose to mark them as deprecated.
> > > >>
> > > >> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky  >
> > > >> wrote:
> > > >>>
> > > >>> Hi, Maxim. And what is the plan of removing this functionality?
> And I
> > > >> also
> > > >>> have some questions regarding deprecation in binary protocol
> > > >>>
> > > >>> Currently thin client binary protocol
> > > >>> 1. Does support LOCAL caches
> > > >>> 2. Does not support node filters.
> > > >>>
> > > >>> I can hardly imagine the usefulness of this feature on thin
> clients,
> > > >>> especially with partition awareness, but nevertheless.
> > > >>> What is expected behaviour if this feature is removed from newest
> > > version
> > > >>> of Apache Ignite server and and and old client is requesting
> > > >>> creation of LOCAL cache?
> > > >>>
> > > >>> вс, 12 сент. 2021 г. в 15:10, Maxim Muzafarov :
> > > >>>
> > >  Folks,
> > > 
> > >  Let's get back to the discussion of obsolete LOCAL caches since a
> > lot
> > >  of time has passed since the last discussion.
> > >  I've created an issue [1] for deprecation. Let's deprecate them at
> > >  least at the next 2.12 release.
> > > 
> > >  WDYT?
> > > 
> > > 
> > >  [1] https://issues.apache.org/jira/browse/IGNITE-15499
> > > 
> > >  On Fri, 27 Jul 2018 at 20:59, Valentin Kulichenko
> > >   wrote:
> > > >
> > > > Guys,
> > > >
> > > > Use cases for local caches are rare, but they definitely exist. I
> > > >> don't
> > > > think it's a very good idea to deprecate this functionality at
> this
> > >  point.
> > > >
> > > > At the same point, it's obviously not the most critical part of
> the
> > > > product, so maintaining the whole separate implementation for it
> is
> > > > probably an overkill. We had exact same story with replicated
> > caches
> > > >> btw
> > >  -
> > > > they were implemented separately which caused maintainability
> > > >> issues, and
> > > > we ended up removing this separate implementation. If we have the
> > > >> same
> > > > situation here, let's use the same solution.
> > > >
> > > > -Val
> > > >
> > > > On Fri, Jul 27, 2018 at 3:05 AM Dmitry Pavlov <
> > dpavlov@gmail.com
> > > >>>
> > >  wrote:
> > > >
> > > >> Hi Dmitriy,
> > > >>
> > > >> I would like to stress this: I'm not saying local cache it
> > > >> useless. I'm
> > > >> supposing it is not used widely. I want to figure out if I'm
> > > >> mistaking.
> > > 

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[18624049226]

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 two issue be merged into the ignite-2.11 branch?

https://issues.apache.org/jira/browse/IGNITE-14404

https://issues.apache.org/jira/browse/IGNITE-15503

在 2021/9/13 17:12, Pavel Tupitsyn 写道:

+1

Downloaded binary packages, started a cluster with a few nodes, tested

new

.NET examples.

On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
   wrote:


Thanks Maxim !
I tries to compare this ver with 2.10 (some performance tests with
persistence and transactional\atomic payload) and seems all ok there.
+1 from me.


Dear Community,


The release candidate for the 2.11 version is ready.


I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/

The following staging can be used for testing:


https://repository.apache.org/content/repositories/orgapacheignite-1526/
https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite

Tag name is 2.11.0-rc2:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2

RELEASE_NOTES:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11

Complete list of resolved issues:


https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11%27

))

DEVNOTES:


https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.11

Additional checks have been performed (available for users included

into

the release group on TeamCity).

TC [Check RC: Licenses, compile, chksum]


https://ci.ignite.apache.org/viewLog.html?buildId=6176219=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=buildResultsDiv

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

+1 - to accept Apache Ignite 2.11.0-rc2
0 - don't care either way
-1 - DO NOT accept Apache Ignite Ignite 2.11.0-rc2 (explain why)

See notes on how to verify release here
https://www.apache.org/info/verification.html
and


https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification

This vote will be open for 4 days until Thu Sep 16, 12:00 2021 (Moscow
time).
Please, write me down the thread if you need additional time to check
the release.


https://www.timeanddate.com/countdown/vote?iso=20210916T12=166=%5BVOTE%5D+Release+Apache+Ignite+2.10.0+RC2=serif=1

Re: Deprecating LOCAL cache

[Anton Vinogradov]

> 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, Sep 14, 2021 at 10:30 AM Ivan Daschinsky 
wrote:

> >> 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) before 2.13 release?
>
> вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov :
>
> > 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 and removing documentation are not
> > > enough.
> > >
> > >
> > > пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov :
> > >
> > >> Ivan,
> > >>
> > >> I don't think we can remove LOCAL caches at the nearest time, so there
> > >> is no plan for that. I can only imagine a single release that will
> > >> contain all the breaking changes we want to apply in 2.x version.
> > >>
> > >> My point here is only about deprecation:
> > >> - there are a lot of motivation points to remove written in this
> thread;
> > >> - I always hear from the support team that they do not recommend using
> > >> local caches;
> > >> - I haven't seen any bugs fixed for a long time for local caches
> > >> (suppose that we are not maintaining them);
> > >>
> > >> I just want to make sure that all these points are reflected in the
> > >> code base, so propose to mark them as deprecated.
> > >>
> > >> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky 
> > >> wrote:
> > >>>
> > >>> Hi, Maxim. And what is the plan of removing this functionality? And I
> > >> also
> > >>> have some questions regarding deprecation in binary protocol
> > >>>
> > >>> Currently thin client binary protocol
> > >>> 1. Does support LOCAL caches
> > >>> 2. Does not support node filters.
> > >>>
> > >>> I can hardly imagine the usefulness of this feature on thin clients,
> > >>> especially with partition awareness, but nevertheless.
> > >>> What is expected behaviour if this feature is removed from newest
> > version
> > >>> of Apache Ignite server and and and old client is requesting
> > >>> creation of LOCAL cache?
> > >>>
> > >>> вс, 12 сент. 2021 г. в 15:10, Maxim Muzafarov :
> > >>>
> >  Folks,
> > 
> >  Let's get back to the discussion of obsolete LOCAL caches since a
> lot
> >  of time has passed since the last discussion.
> >  I've created an issue [1] for deprecation. Let's deprecate them at
> >  least at the next 2.12 release.
> > 
> >  WDYT?
> > 
> > 
> >  [1] https://issues.apache.org/jira/browse/IGNITE-15499
> > 
> >  On Fri, 27 Jul 2018 at 20:59, Valentin Kulichenko
> >   wrote:
> > >
> > > Guys,
> > >
> > > Use cases for local caches are rare, but they definitely exist. I
> > >> don't
> > > think it's a very good idea to deprecate this functionality at this
> >  point.
> > >
> > > At the same point, it's obviously not the most critical part of the
> > > product, so maintaining the whole separate implementation for it is
> > > probably an overkill. We had exact same story with replicated
> caches
> > >> btw
> >  -
> > > they were implemented separately which caused maintainability
> > >> issues, and
> > > we ended up removing this separate implementation. If we have the
> > >> same
> > > situation here, let's use the same solution.
> > >
> > > -Val
> > >
> > > On Fri, Jul 27, 2018 at 3:05 AM Dmitry Pavlov <
> dpavlov@gmail.com
> > >>>
> >  wrote:
> > >
> > >> Hi Dmitriy,
> > >>
> > >> I would like to stress this: I'm not saying local cache it
> > >> useless. I'm
> > >> supposing it is not used widely. I want to figure out if I'm
> > >> mistaking.
> > >>
> > >> All folks involved into user list says it is not used, so why not
> > >> to
> > >> deprecate? If we make a mistake, somebody will come to user list
> > >> and
> >  say,
> > >> 'Hey, why did you deprecate this, it is used for... in my project'
> > >>
> > >> Being very experienced Igniter you probably know real life usage
> >  examples.
> > >> And I appreciate if you or somebody else in community could share
> > >> it.
> > >>
> > >> Sincerely,
> > >> Dmitriy Pavlov
> > >>
> > >> пт, 27 июл. 2018 г. в 1:04, Dmitriy Setrakyan <
> > >> dsetrak...@apache.org>:
> > >>
> > >>> Guys,
> > >>>
> > >>> I just want to make sure we are all on 

Re: [VOTE] Release pyignite 0.5.2-rc0

[Ivan Daschinsky]

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

Checked hashsums and gpg signatures -- passed

пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :

> 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 the link above, you will find source packages (*.tar.gz and
> *.zip)
> and binary packages (wheels) for windows (amd64) and linux (x86_64)
> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.
> Code signing keys can be found here --
> https://downloads.apache.org/ignite/KEYS
> Here you can find instructions how to verify packages
> https://www.apache.org/info/verification.html
>
> You can install binary package for specific version of python using pip
> For example do this on linux for python 3.8
> >> pip install pyignite-0.5.2-cp38-cp38-manylinux1_x86_64.whl
>
> You can build and install package from source using this command:
> >> pip install pyignite-0.5.2.tar.gz
> You can build wheel on your platform using this command:
> >> pip wheel --no-deps pyignite-0.5.2.tar.gz
>
> For building C module, you should have python headers and C compiler
> installed.
> (i.e. for ubuntu sudo apt install build-essential python3-dev)
> In Mac OS X xcode-tools and python from homebrew are the best option.
>
> In order to check whether C module works, use following:
> >> from pyignite import _cutils
> >> print(_cutils.hashcode('test'))
> >> 3556498
>
> You can find documentation here:
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/
>
> You can find examples here (to check them, you should start ignite
> locally):
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.5.2.rc0/examples.html
> Also, examples can be found in source archive in examples subfolder.
> docker-compose.yml is supplied in order to start ignite quickly. (Use
> `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> down` to shut down it)
>
> Release notes:
>
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=a67624a9c141ad5457cdda1a50bd57af5ac62615;hb=1222f29abca4c44a8a2f23e413eafb6acd332e76
>
> Git release tag was created:
>
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.5.2.rc0
>
> The vote is formal, see voting guidelines
> https://www.apache.org/foundation/voting.html
>
> +1 - to accept pyignite-0.5.2-rc0
> 0 - don't care either way
> -1 - DO NOT accept pyignite-0.5.2-rc0
>
> The vote finishes at 09/15/2021 15:00 UTC
>


-- 
Sincerely yours, Ivan Daschinskiy

Re: [VOTE] Release Apache Ignite 2.11.0 RC2

[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 two issue be merged into the ignite-2.11 branch?
>
> https://issues.apache.org/jira/browse/IGNITE-14404
>
> https://issues.apache.org/jira/browse/IGNITE-15503
>
> 在 2021/9/13 17:12, Pavel Tupitsyn 写道:
> > +1
> >
> > Downloaded binary packages, started a cluster with a few nodes, tested
> new
> > .NET examples.
> >
> > On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
> >   wrote:
> >
> >>
> >> Thanks Maxim !
> >> I tries to compare this ver with 2.10 (some performance tests with
> >> persistence and transactional\atomic payload) and seems all ok there.
> >> +1 from me.
> >>
> >>>
> >>> Dear Community,
> >>>
> >>>
> >>> The release candidate for the 2.11 version is ready.
> >>>
> >>>
> >>> I have uploaded a release candidate to:
> >>> https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
> >>> https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/
> >>>
> >>> The following staging can be used for testing:
> >>>
> https://repository.apache.org/content/repositories/orgapacheignite-1526/
> >>>
> >>
> https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
> >>> Tag name is 2.11.0-rc2:
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2
> >>> RELEASE_NOTES:
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11
> >>> Complete list of resolved issues:
> >>>
> >>
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11%27
> >> ))
> >>> DEVNOTES:
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.11
> >>>
> >>> Additional checks have been performed (available for users included
> into
> >>> the release group on TeamCity).
> >>>
> >>> TC [Check RC: Licenses, compile, chksum]
> >>>
> >>
> https://ci.ignite.apache.org/viewLog.html?buildId=6176219=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=buildResultsDiv
> >>>
> >>> The vote is formal, see voting guidelines
> >>> https://www.apache.org/foundation/voting.html
> >>>
> >>> +1 - to accept Apache Ignite 2.11.0-rc2
> >>> 0 - don't care either way
> >>> -1 - DO NOT accept Apache Ignite Ignite 2.11.0-rc2 (explain why)
> >>>
> >>> See notes on how to verify release here
> >>> https://www.apache.org/info/verification.html
> >>> and
> >>>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >>>
> >>> This vote will be open for 4 days until Thu Sep 16, 12:00 2021 (Moscow
> >>> time).
> >>> Please, write me down the thread if you need additional time to check
> >>> the release.
> >>>
> >>
> https://www.timeanddate.com/countdown/vote?iso=20210916T12=166=%5BVOTE%5D+Release+Apache+Ignite+2.10.0+RC2=serif=1
> >>
> >>
> >>
> >>

Re: Deprecating LOCAL cache

[Ivan Daschinsky]

>> 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) before 2.13 release?

вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov :

> 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 and removing documentation are not
> > enough.
> >
> >
> > пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov :
> >
> >> Ivan,
> >>
> >> I don't think we can remove LOCAL caches at the nearest time, so there
> >> is no plan for that. I can only imagine a single release that will
> >> contain all the breaking changes we want to apply in 2.x version.
> >>
> >> My point here is only about deprecation:
> >> - there are a lot of motivation points to remove written in this thread;
> >> - I always hear from the support team that they do not recommend using
> >> local caches;
> >> - I haven't seen any bugs fixed for a long time for local caches
> >> (suppose that we are not maintaining them);
> >>
> >> I just want to make sure that all these points are reflected in the
> >> code base, so propose to mark them as deprecated.
> >>
> >> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky 
> >> wrote:
> >>>
> >>> Hi, Maxim. And what is the plan of removing this functionality? And I
> >> also
> >>> have some questions regarding deprecation in binary protocol
> >>>
> >>> Currently thin client binary protocol
> >>> 1. Does support LOCAL caches
> >>> 2. Does not support node filters.
> >>>
> >>> I can hardly imagine the usefulness of this feature on thin clients,
> >>> especially with partition awareness, but nevertheless.
> >>> What is expected behaviour if this feature is removed from newest
> version
> >>> of Apache Ignite server and and and old client is requesting
> >>> creation of LOCAL cache?
> >>>
> >>> вс, 12 сент. 2021 г. в 15:10, Maxim Muzafarov :
> >>>
>  Folks,
> 
>  Let's get back to the discussion of obsolete LOCAL caches since a lot
>  of time has passed since the last discussion.
>  I've created an issue [1] for deprecation. Let's deprecate them at
>  least at the next 2.12 release.
> 
>  WDYT?
> 
> 
>  [1] https://issues.apache.org/jira/browse/IGNITE-15499
> 
>  On Fri, 27 Jul 2018 at 20:59, Valentin Kulichenko
>   wrote:
> >
> > Guys,
> >
> > Use cases for local caches are rare, but they definitely exist. I
> >> don't
> > think it's a very good idea to deprecate this functionality at this
>  point.
> >
> > At the same point, it's obviously not the most critical part of the
> > product, so maintaining the whole separate implementation for it is
> > probably an overkill. We had exact same story with replicated caches
> >> btw
>  -
> > they were implemented separately which caused maintainability
> >> issues, and
> > we ended up removing this separate implementation. If we have the
> >> same
> > situation here, let's use the same solution.
> >
> > -Val
> >
> > On Fri, Jul 27, 2018 at 3:05 AM Dmitry Pavlov  >>>
>  wrote:
> >
> >> Hi Dmitriy,
> >>
> >> I would like to stress this: I'm not saying local cache it
> >> useless. I'm
> >> supposing it is not used widely. I want to figure out if I'm
> >> mistaking.
> >>
> >> All folks involved into user list says it is not used, so why not
> >> to
> >> deprecate? If we make a mistake, somebody will come to user list
> >> and
>  say,
> >> 'Hey, why did you deprecate this, it is used for... in my project'
> >>
> >> Being very experienced Igniter you probably know real life usage
>  examples.
> >> And I appreciate if you or somebody else in community could share
> >> it.
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> пт, 27 июл. 2018 г. в 1:04, Dmitriy Setrakyan <
> >> dsetrak...@apache.org>:
> >>
> >>> Guys,
> >>>
> >>> I just want to make sure we are all on the same page. The main
> >> use
>  case
> >> for
> >>> LOCAL caches is to have a local hash map querable with SQL and
> >>> automatically persisted to a 3rd party DB.
> >>>
> >>> I want to discourage people from saying "nobody needs some
> >> feature".
>  None
> >>> of the people in this discussion are users of any features - we
> >> are
>  all
> >>> developers of the features. Instead of guessing whether to
> >> deprecate
> >>> something or not, I would actually see if it is even worth a
>  discussion.
> >>> How much effort is required to fix the bug found in the LOCAL
> >> 

Re: Deprecating LOCAL cache

[Nikolay Izhikov]

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 and removing documentation are not
> enough.
> 
> 
> пн, 13 сент. 2021 г. в 13:22, Maxim Muzafarov :
> 
>> Ivan,
>> 
>> I don't think we can remove LOCAL caches at the nearest time, so there
>> is no plan for that. I can only imagine a single release that will
>> contain all the breaking changes we want to apply in 2.x version.
>> 
>> My point here is only about deprecation:
>> - there are a lot of motivation points to remove written in this thread;
>> - I always hear from the support team that they do not recommend using
>> local caches;
>> - I haven't seen any bugs fixed for a long time for local caches
>> (suppose that we are not maintaining them);
>> 
>> I just want to make sure that all these points are reflected in the
>> code base, so propose to mark them as deprecated.
>> 
>> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky 
>> wrote:
>>> 
>>> Hi, Maxim. And what is the plan of removing this functionality? And I
>> also
>>> have some questions regarding deprecation in binary protocol
>>> 
>>> Currently thin client binary protocol
>>> 1. Does support LOCAL caches
>>> 2. Does not support node filters.
>>> 
>>> I can hardly imagine the usefulness of this feature on thin clients,
>>> especially with partition awareness, but nevertheless.
>>> What is expected behaviour if this feature is removed from newest version
>>> of Apache Ignite server and and and old client is requesting
>>> creation of LOCAL cache?
>>> 
>>> вс, 12 сент. 2021 г. в 15:10, Maxim Muzafarov :
>>> 
 Folks,
 
 Let's get back to the discussion of obsolete LOCAL caches since a lot
 of time has passed since the last discussion.
 I've created an issue [1] for deprecation. Let's deprecate them at
 least at the next 2.12 release.
 
 WDYT?
 
 
 [1] https://issues.apache.org/jira/browse/IGNITE-15499
 
 On Fri, 27 Jul 2018 at 20:59, Valentin Kulichenko
  wrote:
> 
> Guys,
> 
> Use cases for local caches are rare, but they definitely exist. I
>> don't
> think it's a very good idea to deprecate this functionality at this
 point.
> 
> At the same point, it's obviously not the most critical part of the
> product, so maintaining the whole separate implementation for it is
> probably an overkill. We had exact same story with replicated caches
>> btw
 -
> they were implemented separately which caused maintainability
>> issues, and
> we ended up removing this separate implementation. If we have the
>> same
> situation here, let's use the same solution.
> 
> -Val
> 
> On Fri, Jul 27, 2018 at 3:05 AM Dmitry Pavlov >> 
 wrote:
> 
>> Hi Dmitriy,
>> 
>> I would like to stress this: I'm not saying local cache it
>> useless. I'm
>> supposing it is not used widely. I want to figure out if I'm
>> mistaking.
>> 
>> All folks involved into user list says it is not used, so why not
>> to
>> deprecate? If we make a mistake, somebody will come to user list
>> and
 say,
>> 'Hey, why did you deprecate this, it is used for... in my project'
>> 
>> Being very experienced Igniter you probably know real life usage
 examples.
>> And I appreciate if you or somebody else in community could share
>> it.
>> 
>> Sincerely,
>> Dmitriy Pavlov
>> 
>> пт, 27 июл. 2018 г. в 1:04, Dmitriy Setrakyan <
>> dsetrak...@apache.org>:
>> 
>>> Guys,
>>> 
>>> I just want to make sure we are all on the same page. The main
>> use
 case
>> for
>>> LOCAL caches is to have a local hash map querable with SQL and
>>> automatically persisted to a 3rd party DB.
>>> 
>>> I want to discourage people from saying "nobody needs some
>> feature".
 None
>>> of the people in this discussion are users of any features - we
>> are
 all
>>> developers of the features. Instead of guessing whether to
>> deprecate
>>> something or not, I would actually see if it is even worth a
 discussion.
>>> How much effort is required to fix the bug found in the LOCAL
>> cache?
>>> 
>>> D.
>>> 
>>> On Thu, Jul 26, 2018 at 12:19 PM, Dmitry Pavlov <
 dpavlov@gmail.com>
>>> wrote:
>>> 
 Hi Alexey,
 
 There is nothing to be sorry about :) Сommunity appreciates an
>>> alternative
 vision, this allows us to make as informed decisions as it
 possible.
 
 Thank you for finding this fact, it is very interesting.
 
 I'm not sure all these examples were prepared by experienced
>> Ignite
>>> users.
 So idea of deprecation may have one more argument. Deprecation
>>