Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

2022-04-26 Thread Nikita Amelchev
+1

вт, 26 апр. 2022 г. в 17:22, Anton Vinogradov :
>
> +1
>
> On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков  wrote:
>
> > +1
> >
> > > 26 апр. 2022 г., в 16:24, Maxim Muzafarov 
> > написал(а):
> > >
> > > Hello Igniters,
> > >
> > >
> > > Currently we have a batch of ignite-hibernate modules which provide
> > > Hibernate second-level cache (L2 cache) implementation based on the
> > > Apache Ignite for different version of hibernate.
> > >
> > > The following list of modules we have:
> > > - ignite-hibernate_4.2
> > > - ignite-hibernate_5.1
> > > - ignite-hibernate_5.3
> > > - ignite-hibernate-core (a common part for all hibernate modules)
> > >
> > > I propose to use the same approach as was used for the
> > > ignite-spring-data module [1] and move all these modules to the Ignite
> > > Extesions project.
> > >
> > > In details:
> > >
> > > - remove all these modules from the Ignite project.
> > > - create ignite-hibernate extension.
> > > - move ignite-hibernate-core + ignite-hibernate_4.2 to
> > > release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> > > extension will be 4.2.0) and release it on demand;
> > > - move ignite-hibernate-core + ignite-hibernate_5.1 to
> > > release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> > > extension will be 5.1.0) and release it on demand;
> > > - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> > > branch and to the release/ignite-hibernate-5.3.0 branch (the version
> > > of ignite-hibernate extension will be 5.3.0) and release it
> > > immediately;
> > >
> > >
> > > Is it OK or am I missing something?
> > > WDYT?
> > >
> > >
> > > [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7
> >
> >



-- 
Best wishes,
Amelchev Nikita


[RESULT] [VOTE] Release Apache Ignite 2.13.0 RC2

2022-04-26 Thread Nikita Amelchev
Dear community,

The release of Apache Ignite 2.13.0 RC2 has been accepted.

Vote result: The vote PASSES with five +1 votes (4 bindings), one +0.5
vote, no 0
votes, and no -1 votes.

+1 votes:
- Zhenya Stanilovsky
- Nikolay Izhikov (binding)
- Ilya Kasnacheev (binding)
- Maxim Muzafarov (binding)
- Alex Plehanov (binding)

+0.5 votes:
- Ivan Daschinsky

The new release will be announced soon.

-- 
Best wishes,
Amelchev Nikita


Re: [VOTE] Release Apache Ignite 2.13.0 RC2

2022-04-26 Thread Alex Plehanov
+1

Built from sources, started 2 nodes cluster, checked some DDL/DML SQL
queries with H2-based and Calcite-based engines.
As earlier mentioned by Ivan there is an issue, ignite-calcite module
requires also slf4j library, but it's absent in the
libs/optional/ignite-calcite directory, so it's not enough to copy only
ignite-calcite from the optional directory, also ignite-slf4j required to
be copied from the optional directory to run Calcite-based engine. I think
it's not a blocker, we can add information to the configuration
instructions in the documentation.



вт, 26 апр. 2022 г. в 12:38, Ivan Daschinsky :

> +0.5
>
> Checked ODBC drivers binaries on windows (32 and 64 bit) using pyodbc and
> python 3.8
> Checked both H2 and Calcite engines (setted in DSN and Connection
> configurations)
>
> Works with issues -- cannot start ignite without copying slf4j-api jar into
> ignite-calcite module. Calcite depends itself on slf4-api, however it is
> not added to the ignite-calcite folder.
>
> I am not sure whether it is a blocker or not. I incline towards not
> rejecting the release due to the minority of the issue.
>
> пн, 25 апр. 2022 г. в 22:23, Maxim Muzafarov :
>
> > +1 (binding)
> >
> > Checked parent project, versions, dependencies.
> >
> > On Mon, 25 Apr 2022 at 12:06, Ilya Kasnacheev  >
> > wrote:
> > >
> > > +1 (binding)
> > >
> > > Ran a slim node, built from sources, built and ran c++ node.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > пн, 25 апр. 2022 г. в 08:55, Николай Ижиков :
> > >
> > > > +1 (binding)
> > > >
> > > > > 23 апр. 2022 г., в 17:32, Nikita Amelchev 
> > > > написал(а):
> > > > >
> > > > > Hi Igniters, PMCs,
> > > > >
> > > > > Please, verify a new release candidate.
> > > > >
> > > > > The vote will continue until there are enough votes for a
> > resolution. [1]
> > > > >
> > > > > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
> > > > >
> > > > > пт, 22 апр. 2022 г. в 08:24, Zhenya Stanilovsky
> > > > :
> > > > >>
> > > > >>
> > > > >> Nikita thanks for your effort !
> > > > >> Download sources, run examples.
> > > > >> +1 from me.
> > > > >>
> > > > >>> Dear Community,
> > > > >>>
> > > > >>> The release candidate is ready.
> > > > >>>
> > > > >>> I have uploaded a release candidate to:
> > > > >>> https://dist.apache.org/repos/dist/dev/ignite/2.13.0-rc2/
> > > > >>>
> https://dist.apache.org/repos/dist/dev/ignite/packages_2.13.0-rc2/
> > > > >>>
> > > > >>> The following staging can be used for testing:
> > > > >>>
> > > >
> > https://repository.apache.org/content/repositories/orgapacheignite-1542
> > > > >>>
> > > > >>> Tag name is 2.13.0-rc1:
> > > > >>>
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.13.0-rc2
> > > > >>>
> > > > >>> RELEASE_NOTES:
> > > > >>>
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.13
> > > > >>>
> > > > >>> 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.13%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> > > > >>>
> > > > >>> DEVNOTES:
> > > > >>>
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.13
> > > > >>>
> > > > >>> Additional checks have been performed (available for users
> included
> > > > >>> into the release group on TeamCity).
> > > > >>>
> > > > >>> TC [Check RC: Licenses, compile, chksum]
> > > > >>>
> > > >
> >
> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6399934
> > > > >>>
> > > > >>> TC [2] Compare w/ Previous Release
> > > > >>>
> > > >
> >
> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6399932
> > > > >>>
> > > > >>> The vote is formal, see voting guidelines
> > > > >>> https://www.apache.org/foundation/voting.html
> > > > >>>
> > > > >>> +1 - to accept Apache Ignite 2.13.0-rc2
> > > > >>> 0 - don't care either way
> > > > >>> -1 - DO NOT accept Apache Ignite Ignite 2.13.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 at least 3 days till Fri Apr 23, 2022,
> > > > >>> 20:00 UTC. Please, write me down the thread if you need
> additional
> > > > >>> time to check the
> > > > >>> release.
> > > > >>>
> > > >
> >
> https://www.timeanddate.com/countdown/vote?iso=20220423T20=0=VOTE+on+the+Apache+Ignite+Release+2.13.0+RC2=sanserif
> > > > >>>
> > > > >>> --
> > > > >>> Best wishes,
> > > > >>> 

Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

2022-04-26 Thread Anton Vinogradov
+1

On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков  wrote:

> +1
>
> > 26 апр. 2022 г., в 16:24, Maxim Muzafarov 
> написал(а):
> >
> > Hello Igniters,
> >
> >
> > Currently we have a batch of ignite-hibernate modules which provide
> > Hibernate second-level cache (L2 cache) implementation based on the
> > Apache Ignite for different version of hibernate.
> >
> > The following list of modules we have:
> > - ignite-hibernate_4.2
> > - ignite-hibernate_5.1
> > - ignite-hibernate_5.3
> > - ignite-hibernate-core (a common part for all hibernate modules)
> >
> > I propose to use the same approach as was used for the
> > ignite-spring-data module [1] and move all these modules to the Ignite
> > Extesions project.
> >
> > In details:
> >
> > - remove all these modules from the Ignite project.
> > - create ignite-hibernate extension.
> > - move ignite-hibernate-core + ignite-hibernate_4.2 to
> > release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> > extension will be 4.2.0) and release it on demand;
> > - move ignite-hibernate-core + ignite-hibernate_5.1 to
> > release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> > extension will be 5.1.0) and release it on demand;
> > - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> > branch and to the release/ignite-hibernate-5.3.0 branch (the version
> > of ignite-hibernate extension will be 5.3.0) and release it
> > immediately;
> >
> >
> > Is it OK or am I missing something?
> > WDYT?
> >
> >
> > [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7
>
>


Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

2022-04-26 Thread Николай Ижиков
+1

> 26 апр. 2022 г., в 16:24, Maxim Muzafarov  написал(а):
> 
> Hello Igniters,
> 
> 
> Currently we have a batch of ignite-hibernate modules which provide
> Hibernate second-level cache (L2 cache) implementation based on the
> Apache Ignite for different version of hibernate.
> 
> The following list of modules we have:
> - ignite-hibernate_4.2
> - ignite-hibernate_5.1
> - ignite-hibernate_5.3
> - ignite-hibernate-core (a common part for all hibernate modules)
> 
> I propose to use the same approach as was used for the
> ignite-spring-data module [1] and move all these modules to the Ignite
> Extesions project.
> 
> In details:
> 
> - remove all these modules from the Ignite project.
> - create ignite-hibernate extension.
> - move ignite-hibernate-core + ignite-hibernate_4.2 to
> release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> extension will be 4.2.0) and release it on demand;
> - move ignite-hibernate-core + ignite-hibernate_5.1 to
> release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> extension will be 5.1.0) and release it on demand;
> - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> branch and to the release/ignite-hibernate-5.3.0 branch (the version
> of ignite-hibernate extension will be 5.3.0) and release it
> immediately;
> 
> 
> Is it OK or am I missing something?
> WDYT?
> 
> 
> [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7



[DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

2022-04-26 Thread Maxim Muzafarov
Hello Igniters,


Currently we have a batch of ignite-hibernate modules which provide
Hibernate second-level cache (L2 cache) implementation based on the
Apache Ignite for different version of hibernate.

The following list of modules we have:
- ignite-hibernate_4.2
- ignite-hibernate_5.1
- ignite-hibernate_5.3
- ignite-hibernate-core (a common part for all hibernate modules)

I propose to use the same approach as was used for the
ignite-spring-data module [1] and move all these modules to the Ignite
Extesions project.

In details:

- remove all these modules from the Ignite project.
- create ignite-hibernate extension.
- move ignite-hibernate-core + ignite-hibernate_4.2 to
release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
extension will be 4.2.0) and release it on demand;
- move ignite-hibernate-core + ignite-hibernate_5.1 to
release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
extension will be 5.1.0) and release it on demand;
- move ignite-hibernate-core + ignite-hibernate_5.3 to the master
branch and to the release/ignite-hibernate-5.3.0 branch (the version
of ignite-hibernate extension will be 5.3.0) and release it
immediately;


Is it OK or am I missing something?
WDYT?


[1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7


Re: Slack

2022-04-26 Thread Kseniya Romanova
Hi Duarte! I've invited you to the Ignite channel,  but as I can see we
have more discussions here (and here experts reply faster).

пн, 25 апр. 2022 г. в 20:36, Duarte Machado :

> Hello, I'm writing as I have a project that relies on apache ignite and in
> the slack page it says to gain access we need to request it from
> someone who already has access to it. I'd like to be able to discuss the
> viability of some of our modifications, as well as keep track of the
> development process to better plan our project management tasks. Thank you
>


Re: [VOTE] Release Apache Ignite 2.13.0 RC2

2022-04-26 Thread Ivan Daschinsky
+0.5

Checked ODBC drivers binaries on windows (32 and 64 bit) using pyodbc and
python 3.8
Checked both H2 and Calcite engines (setted in DSN and Connection
configurations)

Works with issues -- cannot start ignite without copying slf4j-api jar into
ignite-calcite module. Calcite depends itself on slf4-api, however it is
not added to the ignite-calcite folder.

I am not sure whether it is a blocker or not. I incline towards not
rejecting the release due to the minority of the issue.

пн, 25 апр. 2022 г. в 22:23, Maxim Muzafarov :

> +1 (binding)
>
> Checked parent project, versions, dependencies.
>
> On Mon, 25 Apr 2022 at 12:06, Ilya Kasnacheev 
> wrote:
> >
> > +1 (binding)
> >
> > Ran a slim node, built from sources, built and ran c++ node.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 25 апр. 2022 г. в 08:55, Николай Ижиков :
> >
> > > +1 (binding)
> > >
> > > > 23 апр. 2022 г., в 17:32, Nikita Amelchev 
> > > написал(а):
> > > >
> > > > Hi Igniters, PMCs,
> > > >
> > > > Please, verify a new release candidate.
> > > >
> > > > The vote will continue until there are enough votes for a
> resolution. [1]
> > > >
> > > > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
> > > >
> > > > пт, 22 апр. 2022 г. в 08:24, Zhenya Stanilovsky
> > > :
> > > >>
> > > >>
> > > >> Nikita thanks for your effort !
> > > >> Download sources, run examples.
> > > >> +1 from me.
> > > >>
> > > >>> Dear Community,
> > > >>>
> > > >>> The release candidate is ready.
> > > >>>
> > > >>> I have uploaded a release candidate to:
> > > >>> https://dist.apache.org/repos/dist/dev/ignite/2.13.0-rc2/
> > > >>> https://dist.apache.org/repos/dist/dev/ignite/packages_2.13.0-rc2/
> > > >>>
> > > >>> The following staging can be used for testing:
> > > >>>
> > >
> https://repository.apache.org/content/repositories/orgapacheignite-1542
> > > >>>
> > > >>> Tag name is 2.13.0-rc1:
> > > >>>
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.13.0-rc2
> > > >>>
> > > >>> RELEASE_NOTES:
> > > >>>
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.13
> > > >>>
> > > >>> 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.13%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> > > >>>
> > > >>> DEVNOTES:
> > > >>>
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.13
> > > >>>
> > > >>> Additional checks have been performed (available for users included
> > > >>> into the release group on TeamCity).
> > > >>>
> > > >>> TC [Check RC: Licenses, compile, chksum]
> > > >>>
> > >
> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6399934
> > > >>>
> > > >>> TC [2] Compare w/ Previous Release
> > > >>>
> > >
> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6399932
> > > >>>
> > > >>> The vote is formal, see voting guidelines
> > > >>> https://www.apache.org/foundation/voting.html
> > > >>>
> > > >>> +1 - to accept Apache Ignite 2.13.0-rc2
> > > >>> 0 - don't care either way
> > > >>> -1 - DO NOT accept Apache Ignite Ignite 2.13.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 at least 3 days till Fri Apr 23, 2022,
> > > >>> 20:00 UTC. Please, write me down the thread if you need additional
> > > >>> time to check the
> > > >>> release.
> > > >>>
> > >
> https://www.timeanddate.com/countdown/vote?iso=20220423T20=0=VOTE+on+the+Apache+Ignite+Release+2.13.0+RC2=sanserif
> > > >>>
> > > >>> --
> > > >>> Best wishes,
> > > >>> Amelchev Nikita
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Best wishes,
> > > > Amelchev Nikita
> > >
> > >
>


-- 
Sincerely yours, Ivan Daschinskiy


Re: Ignite Summit 2022: The Call for Papers is Open!

2022-04-26 Thread Kseniya Romanova
Igniters, just a reminder: this is the last week of CFP.
If you have a good Ignite story to share, submit it here:
https://sessionize.com/IgniteSummit-2022

Cheers,
Kseniya

пн, 7 февр. 2022 г. в 22:15, Kseniya Romanova :

> Hi, Igniters!
>
> Hosted by GridGain Systems with the Apache Software Foundation as a
> Community Partner, Ignite Summit[1] was the biggest community event in
> 2021[2][3]. And we will meet again on June 14, 2022, to shine the
> spotlight on Apache Ignite! The idea is to share architectural best
> practices from Ignite users' experience, meet Ignite developers, and
> develop expertise. The event is virtual and free of charge.
>
> We are now accepting proposals for 30-minutes talks and 15-minutes
> lightning talks:
>
>
>-
>
>Apache Ignite user story
>-
>
>An Ignite architectural deep dive
>-
>
>The experience of integrating Apache Ignite with other technologies
>-
>
>The use of Apache Ignite in a cloud environment
>-
>
>Apache Ignite monitoring and troubleshooting
>
>
> Please submit your proposal via https://sessionize.com/IgniteSummit-2022 
> before
> April 29.
>
> You can help to promote Summit by sharing a Twitter[4] or LinkedIn[5]
> post. Also, join the LinkedIn event[6] to receive the updates.
>
> If you have any questions about attending or speaking at the Summit, I
> would be happy to answer.
>
> Cheers,
>
> Kseniya
>
> [1] https://ignite-summit.org
>
> [2] Ignite Summit 2021 recordings
> https://www.youtube.com/playlist?list=PLMc7NR20hA-KF8c_hVICKpzKnWkjzfC2V
>
> [3]Ignite Summit 2021: Cloud Edition recordings
> https://www.youtube.com/playlist?list=PLMc7NR20hA-JvgLWtvp2R9tEnD5vlp9l0
>
> [4]https://twitter.com/ApacheIgnite/status/1490741175548002314
>
> [5]
> https://www.linkedin.com/feed/update/urn:li:activity:6896497935580770304
> [6] https://www.linkedin.com/events/6896527308195528704/about/
>


A new feedback has been added : 74

2022-04-26 Thread Bugyard
A new feedback has been added, go to bugyard.io to see all the details...

https://bugyard.io

A new feedback has been added 

"This is not correct and inline with the documentation mentionend above. 
value="ignite". This needs to be changed."   by tony.tromp 

View feedback 
https://app.bugyard.io/web/app/rycqZJDyY/f/62665eb034707000142713b5

A new feedback has been added : 75

2022-04-26 Thread Bugyard
A new feedback has been added, go to bugyard.io to see all the details...

https://bugyard.io

A new feedback has been added 

"This is not correct and inline with the documentation mentionend above. This 
needs to be changed to value="ignite-service". "   by tony.tromp 

View feedback 
https://app.bugyard.io/web/app/rycqZJDyY/f/62665efa34707000142713b9