[ANNOUNCE] Apache IGNITE python thin client (pyignite) 0.5.2 released

2021-09-17 Thread Ivan Daschinsky
The Apache Ignite Community is pleased to announce the release of Apache IGNITE python thin client (pyignite) 0.5.2. This new release of python thin client contains bugfixes and it is recommended to update. Namely: 1. Fixed incorrect partial read from socket in sync client 1. Fixed nested object a

Re: [RESULT] [VOTE] Release pyignite 0.5.2-rc0

2021-09-17 Thread Maxim Muzafarov
Ivan, I've found that the versions below have 'unreleased' status in the Apache JIRA. Can you please share a release date for each version and I'll mark them as 'released'? python-0.5.2 python-0.5.1 python-0.5.0 On Thu, 16 Sept 2021 at 09:44, Ivan Daschinsky wrote: > > Hello, Igniters! > > Rele

Re: [RESULT] [VOTE] Release pyignite 0.5.2-rc0

2021-09-17 Thread Ivan Daschinsky
I've done, thank you пт, 17 сент. 2021 г. в 13:44, Maxim Muzafarov : > Ivan, > > I've found that the versions below have 'unreleased' status in the > Apache JIRA. Can you please share a release date for each version and > I'll mark them as 'released'? > > python-0.5.2 > python-0.5.1 > python-0.5.

Re: Request for new TC suite

2021-09-17 Thread Maksim Timonin
FYI, the IndexQuery PR merged. New TC suite [1] now is part of RunAll. [1] https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_IndexQueryApi On Wed, Sep 15, 2021 at 5:29 PM Maksim Timonin wrote: > It has not to be before merge. After merge we will add it to RunAll. > > On Wed, Se

Re: [DISCUSS] IEP-71 Public API for secondary index search

2021-09-17 Thread Maksim Timonin
Hi! The patch merged (IndexQuery with required index name). A lot of thanks to Andrew Mashenkov, Taras Ledkov and Alex Plekhanov for their time and reviews. By the way, I'd like to up the discussion about the optionality of the indexName param for creating IndexQuery. I believe that it's a useful

[DISCUSSION] Separate Jira project and Confluence space for Ignite 3

2021-09-17 Thread Valentin Kulichenko
Igniters, I think it's clear to all of us that Ignite 2.x and 3.x will coexist for a while. They are developed in separate Git repos, but we still accumulate the tickets for both versions in the same Jira project, which seems to complicate the ticket management. For example, we use the "ignite-3"

Re: [DISCUSSION] Separate Jira project and Confluence space for Ignite 3

2021-09-17 Thread Nikita Ivanov
+1 -- Nikita Ivanov On Fri, Sep 17, 2021 at 6:22 PM Valentin Kulichenko wrote: > > Igniters, > > I think it's clear to all of us that Ignite 2.x and 3.x will coexist for a > while. They are developed in separate Git repos, but we still accumulate > the tickets for both versions in the same Jira p