[MTCGA]: new failures in builds [6473335] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master Yarn https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Yarn?branch=%3Cdefault%3E Changes may lead to failure were done by - roman puchkovskiy https://ci2.ignite.apache.org/viewModification.html?modId=956300 - maxim muzafarov https://ci2.ignite.apache.org/viewModification.html?modId=956312 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 03:38:19 09-06-2022
[MTCGA]: new failures in builds [6472700] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master IgniteWalRebalanceTest.testWithGlobalWalChange https://ci2.ignite.apache.org/test/690561471127920978?currentProjectId=IgniteTests24Java8=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 21:08:20 08-06-2022
Re: .NET Build and Versioning Improvements
Folks, Make sense. Another tricky question is - can we have the following version committed in the source files 2.14.0.0, but when the 'release' profile get activated (or probably the build happened) revision number will changed to 2.14.0.62943? This will be the final release version ready for deploy (with the last digits changed each time build happened). On Wed, 8 Jun 2022 at 16:54, Pavel Tupitsyn wrote: > > > As for the last number in .NET version, AFAIK it is used as the unique > > build id and is required for nightly builds as nuget doesn't have > > functionality a-la maven's 'snapshots' > > NuGet supports string suffixes like 2.15.0-nightly1. However, > AssemblyVersionAttribute does not. > In some cases it is important to avoid having different NuGet packages with > assemblies that have the AssemblyVersion inside (dll hell type problems, > especially with peer assembly loading). > > So I suggest keeping the last number for AssemblyVersion > and AssemblyFileVersion in SharedAssemblyInfo. > This does not affect the NuGet package version. > > Otherwise, I don't have any objections to adding a new Maven step that > builds dotnet, as long as we keep using build.ps1 script. > > Thanks, > Pavel > > On Wed, Jun 8, 2022 at 4:31 PM Ivan Daschinsky wrote: > > > As for the last number in .NET version, AFAIK it is used as the unique > > build id and is required for nightly builds as nuget doesn't have > > functionality a-la maven's 'snapshots' > > > > ср, 8 июн. 2022 г. в 16:07, Ivan Daschinsky : > > > > > Since nuget packages have been built on the same linux agent as the main > > > release, it sounds logical to me that this step can be done within the > > > maven lifecycle. > > > I am for it, +1 > > > > > > ср, 8 июн. 2022 г. в 15:13, Maxim Muzafarov : > > > > > >> Hello Igniters, > > >> > > >> > > >> I'd like to simplify the release build for the Apache Ignite. > > >> > > >> My suggestion here are: > > >> 1. Mavenize the building procedure of the 'platform/donet' thin client > > >> (use maven with Ant task) > > >> 2. Change it's versions to fit the Ignite style. > > >> > > >> > > >> = 1. Build = > > >> > > >> Add a pom.xml sub-project with a corresponding maven-ant-plugin with a > > >> Ant task to build the .NET project when the Apache Ignite project > > >> build. We can use here a profile like the numa-allocator does if > > >> building the .NET is note required. > > >> > > >> Such a technique will also allow a variables substitution like the > > >> maven-resource-plugin works (e.g. version substitution). > > >> > > >> Here is an example of how it can be achieved: > > >> > > >> > > https://github.com/apache/ignite/pull/9497/files#diff-77baf2378aa83911a8c3091814db3ff60b7bf328c4ab4850f707717ed96f3d92R107 > > >> > > >> > > >> = 2. Versioning = > > >> > > >> Currently, the version of .NET thin client (SharedAssemblyInfo.cs [1]) > > >> have the following format: > > >> 2.14.0.62943 . The format of .NET versions Major.Minor.Patch.Revision > > >> (described here [2]). > > >> > > >> Since the Apache Ignite doesn't have a dedicated releases for the .NET > > >> thin client I think the last 'Revision' digits can be always set to > > >> zero. So the result version can be: > > >> 2.14.0.0 > > >> > > >> This will allow having the variable substitution also for the version > > >> number and omitt the update-version profile usage for the .NET client. > > >> > > >> > > >> = Advantages = > > >> > > >> - Reduce the code complexity for changing a project version (we don't > > >> need the update-versions maven profile); > > >> - Build the whole project on the local environment and prepare nuget > > >> for the release with a single command; > > >> > > >> > > >> [1] > > >> > > https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/SharedAssemblyInfo.cs > > >> [2] > > >> > > https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#where-nugetversion-diverges-from-semantic-versioning > > >> > > > > > > > > > -- > > > Sincerely yours, Ivan Daschinskiy > > > > > > > > > -- > > Sincerely yours, Ivan Daschinskiy > >
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Alexander, It looks like a blocker. The issue has been targeted to alpha5 release. On Wed, Jun 8, 2022 at 7:30 PM Alexander Polovtcev wrote: > > Hello, dear Igniters. > I've discovered a bug regarding the Pluggable Storage Engines feature. > Please consider adding it to the release scope: > https://issues.apache.org/jira/browse/IGNITE-17139 > > On Mon, Jun 6, 2022 at 5:56 PM Andrey Gura wrote: > > > Igniters, > > > > our release schedule has shifted a bit. But it is time for a code > > freeze and a new branch creation. > > > > The following issues is still in progress (not an issues status, but > > work state): > > > > Data rebalancing > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > CLI MVP > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > SQL API: Implement query metadata > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > SQL API: Add batched DML queries support. > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > SQL API: Examples. > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > Please, give some planned timelines for these issues. I would like to > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > Otherwise, extra steps will be required to include the PR's to the > > release branch. > > > > Thanks! > > > > > -- > With regards, > Aleksandr Polovtcev
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Hello, dear Igniters. I've discovered a bug regarding the Pluggable Storage Engines feature. Please consider adding it to the release scope: https://issues.apache.org/jira/browse/IGNITE-17139 On Mon, Jun 6, 2022 at 5:56 PM Andrey Gura wrote: > Igniters, > > our release schedule has shifted a bit. But it is time for a code > freeze and a new branch creation. > > The following issues is still in progress (not an issues status, but > work state): > > Data rebalancing > https://issues.apache.org/jira/browse/IGNITE-14209 > > CLI MVP > https://issues.apache.org/jira/browse/IGNITE-16971 > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > https://issues.apache.org/jira/browse/IGNITE-17107 > > SQL API: Implement query metadata > https://issues.apache.org/jira/browse/IGNITE-16962 > > SQL API: Add batched DML queries support. > https://issues.apache.org/jira/browse/IGNITE-16963 > > SQL API: Examples. > https://issues.apache.org/jira/browse/IGNITE-17088 > > Please, give some planned timelines for these issues. I would like to > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > Otherwise, extra steps will be required to include the PR's to the > release branch. > > Thanks! > -- With regards, Aleksandr Polovtcev
Re: .NET Build and Versioning Improvements
> As for the last number in .NET version, AFAIK it is used as the unique > build id and is required for nightly builds as nuget doesn't have > functionality a-la maven's 'snapshots' NuGet supports string suffixes like 2.15.0-nightly1. However, AssemblyVersionAttribute does not. In some cases it is important to avoid having different NuGet packages with assemblies that have the AssemblyVersion inside (dll hell type problems, especially with peer assembly loading). So I suggest keeping the last number for AssemblyVersion and AssemblyFileVersion in SharedAssemblyInfo. This does not affect the NuGet package version. Otherwise, I don't have any objections to adding a new Maven step that builds dotnet, as long as we keep using build.ps1 script. Thanks, Pavel On Wed, Jun 8, 2022 at 4:31 PM Ivan Daschinsky wrote: > As for the last number in .NET version, AFAIK it is used as the unique > build id and is required for nightly builds as nuget doesn't have > functionality a-la maven's 'snapshots' > > ср, 8 июн. 2022 г. в 16:07, Ivan Daschinsky : > > > Since nuget packages have been built on the same linux agent as the main > > release, it sounds logical to me that this step can be done within the > > maven lifecycle. > > I am for it, +1 > > > > ср, 8 июн. 2022 г. в 15:13, Maxim Muzafarov : > > > >> Hello Igniters, > >> > >> > >> I'd like to simplify the release build for the Apache Ignite. > >> > >> My suggestion here are: > >> 1. Mavenize the building procedure of the 'platform/donet' thin client > >> (use maven with Ant task) > >> 2. Change it's versions to fit the Ignite style. > >> > >> > >> = 1. Build = > >> > >> Add a pom.xml sub-project with a corresponding maven-ant-plugin with a > >> Ant task to build the .NET project when the Apache Ignite project > >> build. We can use here a profile like the numa-allocator does if > >> building the .NET is note required. > >> > >> Such a technique will also allow a variables substitution like the > >> maven-resource-plugin works (e.g. version substitution). > >> > >> Here is an example of how it can be achieved: > >> > >> > https://github.com/apache/ignite/pull/9497/files#diff-77baf2378aa83911a8c3091814db3ff60b7bf328c4ab4850f707717ed96f3d92R107 > >> > >> > >> = 2. Versioning = > >> > >> Currently, the version of .NET thin client (SharedAssemblyInfo.cs [1]) > >> have the following format: > >> 2.14.0.62943 . The format of .NET versions Major.Minor.Patch.Revision > >> (described here [2]). > >> > >> Since the Apache Ignite doesn't have a dedicated releases for the .NET > >> thin client I think the last 'Revision' digits can be always set to > >> zero. So the result version can be: > >> 2.14.0.0 > >> > >> This will allow having the variable substitution also for the version > >> number and omitt the update-version profile usage for the .NET client. > >> > >> > >> = Advantages = > >> > >> - Reduce the code complexity for changing a project version (we don't > >> need the update-versions maven profile); > >> - Build the whole project on the local environment and prepare nuget > >> for the release with a single command; > >> > >> > >> [1] > >> > https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/SharedAssemblyInfo.cs > >> [2] > >> > https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#where-nugetversion-diverges-from-semantic-versioning > >> > > > > > > -- > > Sincerely yours, Ivan Daschinskiy > > > > > -- > Sincerely yours, Ivan Daschinskiy >
Re: .NET Build and Versioning Improvements
As for the last number in .NET version, AFAIK it is used as the unique build id and is required for nightly builds as nuget doesn't have functionality a-la maven's 'snapshots' ср, 8 июн. 2022 г. в 16:07, Ivan Daschinsky : > Since nuget packages have been built on the same linux agent as the main > release, it sounds logical to me that this step can be done within the > maven lifecycle. > I am for it, +1 > > ср, 8 июн. 2022 г. в 15:13, Maxim Muzafarov : > >> Hello Igniters, >> >> >> I'd like to simplify the release build for the Apache Ignite. >> >> My suggestion here are: >> 1. Mavenize the building procedure of the 'platform/donet' thin client >> (use maven with Ant task) >> 2. Change it's versions to fit the Ignite style. >> >> >> = 1. Build = >> >> Add a pom.xml sub-project with a corresponding maven-ant-plugin with a >> Ant task to build the .NET project when the Apache Ignite project >> build. We can use here a profile like the numa-allocator does if >> building the .NET is note required. >> >> Such a technique will also allow a variables substitution like the >> maven-resource-plugin works (e.g. version substitution). >> >> Here is an example of how it can be achieved: >> >> https://github.com/apache/ignite/pull/9497/files#diff-77baf2378aa83911a8c3091814db3ff60b7bf328c4ab4850f707717ed96f3d92R107 >> >> >> = 2. Versioning = >> >> Currently, the version of .NET thin client (SharedAssemblyInfo.cs [1]) >> have the following format: >> 2.14.0.62943 . The format of .NET versions Major.Minor.Patch.Revision >> (described here [2]). >> >> Since the Apache Ignite doesn't have a dedicated releases for the .NET >> thin client I think the last 'Revision' digits can be always set to >> zero. So the result version can be: >> 2.14.0.0 >> >> This will allow having the variable substitution also for the version >> number and omitt the update-version profile usage for the .NET client. >> >> >> = Advantages = >> >> - Reduce the code complexity for changing a project version (we don't >> need the update-versions maven profile); >> - Build the whole project on the local environment and prepare nuget >> for the release with a single command; >> >> >> [1] >> https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/SharedAssemblyInfo.cs >> [2] >> https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#where-nugetversion-diverges-from-semantic-versioning >> > > > -- > Sincerely yours, Ivan Daschinskiy > -- Sincerely yours, Ivan Daschinskiy
Re: .NET Build and Versioning Improvements
Since nuget packages have been built on the same linux agent as the main release, it sounds logical to me that this step can be done within the maven lifecycle. I am for it, +1 ср, 8 июн. 2022 г. в 15:13, Maxim Muzafarov : > Hello Igniters, > > > I'd like to simplify the release build for the Apache Ignite. > > My suggestion here are: > 1. Mavenize the building procedure of the 'platform/donet' thin client > (use maven with Ant task) > 2. Change it's versions to fit the Ignite style. > > > = 1. Build = > > Add a pom.xml sub-project with a corresponding maven-ant-plugin with a > Ant task to build the .NET project when the Apache Ignite project > build. We can use here a profile like the numa-allocator does if > building the .NET is note required. > > Such a technique will also allow a variables substitution like the > maven-resource-plugin works (e.g. version substitution). > > Here is an example of how it can be achieved: > > https://github.com/apache/ignite/pull/9497/files#diff-77baf2378aa83911a8c3091814db3ff60b7bf328c4ab4850f707717ed96f3d92R107 > > > = 2. Versioning = > > Currently, the version of .NET thin client (SharedAssemblyInfo.cs [1]) > have the following format: > 2.14.0.62943 . The format of .NET versions Major.Minor.Patch.Revision > (described here [2]). > > Since the Apache Ignite doesn't have a dedicated releases for the .NET > thin client I think the last 'Revision' digits can be always set to > zero. So the result version can be: > 2.14.0.0 > > This will allow having the variable substitution also for the version > number and omitt the update-version profile usage for the .NET client. > > > = Advantages = > > - Reduce the code complexity for changing a project version (we don't > need the update-versions maven profile); > - Build the whole project on the local environment and prepare nuget > for the release with a single command; > > > [1] > https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/SharedAssemblyInfo.cs > [2] > https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#where-nugetversion-diverges-from-semantic-versioning > -- Sincerely yours, Ivan Daschinskiy
Re[2]: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Please merge the remaining doc issue https://issues.apache.org/jira/browse/IGNITE-17106 >Среда, 8 июня 2022, 15:58 +04:00 от Andrey Gura : > >Thanks, Yuri! > >On Wed, Jun 8, 2022 at 1:48 PM Юрий < jury.gerzhedow...@gmail.com > wrote: >> >> Seems SQL API: Add batched DML queries support [1] will be moved to next >> alpha, so pleas don't waiting for it. >> >> In the same time SQL API: Examples [2] already done and merged to alpha 5 >> branch. >> >> [1] https://issues.apache.org/jira/browse/IGNITE-16963 >> [2] https://issues.apache.org/jira/browse/IGNITE-17088 >> >> пн, 6 июн. 2022 г. в 22:52, Andrey Gura < ag...@apache.org >: >> >> > Igniters, >> > >> > ignite-3.0.0-alpha5 release branch has been created. But the following >> > issues are still in progress: >> > >> > Data rebalancing >> > https://issues.apache.org/jira/browse/IGNITE-14209 >> > >> > SQL API: Add batched DML queries support. >> > https://issues.apache.org/jira/browse/IGNITE-16963 >> > >> > SQL API: Examples. >> > https://issues.apache.org/jira/browse/IGNITE-17088 >> > >> > Please, make sure these commits will be merged to the main and to the >> > release branch. >> > >> > Thanks! >> > >> > On Mon, Jun 6, 2022 at 6:02 PM Aleksandr Pakhomov < apk...@gmail.com > >> > wrote: >> > > >> > > Hi Andrey, >> > > >> > > As for CLI MVP, the planned timeline is today till 21:00. >> > > Probably, will be ready in an hour. Just waiting for CI build. >> > > >> > > Best regards, >> > > Aleksandr >> > > >> > > > On 6 Jun 2022, at 17:56, Andrey Gura < ag...@apache.org > wrote: >> > > > >> > > > Igniters, >> > > > >> > > > our release schedule has shifted a bit. But it is time for a code >> > > > freeze and a new branch creation. >> > > > >> > > > The following issues is still in progress (not an issues status, but >> > > > work state): >> > > > >> > > > Data rebalancing >> > > > https://issues.apache.org/jira/browse/IGNITE-14209 >> > > > >> > > > CLI MVP >> > > > https://issues.apache.org/jira/browse/IGNITE-16971 >> > > > >> > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory >> > > > https://issues.apache.org/jira/browse/IGNITE-17107 >> > > > >> > > > SQL API: Implement query metadata >> > > > https://issues.apache.org/jira/browse/IGNITE-16962 >> > > > >> > > > SQL API: Add batched DML queries support. >> > > > https://issues.apache.org/jira/browse/IGNITE-16963 >> > > > >> > > > SQL API: Examples. >> > > > https://issues.apache.org/jira/browse/IGNITE-17088 >> > > > >> > > > Please, give some planned timelines for these issues. I would like to >> > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. >> > > > Otherwise, extra steps will be required to include the PR's to the >> > > > release branch. >> > > > >> > > > Thanks! >> > > >> > >> >> >> -- >> Живи с улыбкой! :D -- Igor Gusev
.NET Build and Versioning Improvements
Hello Igniters, I'd like to simplify the release build for the Apache Ignite. My suggestion here are: 1. Mavenize the building procedure of the 'platform/donet' thin client (use maven with Ant task) 2. Change it's versions to fit the Ignite style. = 1. Build = Add a pom.xml sub-project with a corresponding maven-ant-plugin with a Ant task to build the .NET project when the Apache Ignite project build. We can use here a profile like the numa-allocator does if building the .NET is note required. Such a technique will also allow a variables substitution like the maven-resource-plugin works (e.g. version substitution). Here is an example of how it can be achieved: https://github.com/apache/ignite/pull/9497/files#diff-77baf2378aa83911a8c3091814db3ff60b7bf328c4ab4850f707717ed96f3d92R107 = 2. Versioning = Currently, the version of .NET thin client (SharedAssemblyInfo.cs [1]) have the following format: 2.14.0.62943 . The format of .NET versions Major.Minor.Patch.Revision (described here [2]). Since the Apache Ignite doesn't have a dedicated releases for the .NET thin client I think the last 'Revision' digits can be always set to zero. So the result version can be: 2.14.0.0 This will allow having the variable substitution also for the version number and omitt the update-version profile usage for the .NET client. = Advantages = - Reduce the code complexity for changing a project version (we don't need the update-versions maven profile); - Build the whole project on the local environment and prepare nuget for the release with a single command; [1] https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/SharedAssemblyInfo.cs [2] https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#where-nugetversion-diverges-from-semantic-versioning
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Thanks, Yuri! On Wed, Jun 8, 2022 at 1:48 PM Юрий wrote: > > Seems SQL API: Add batched DML queries support [1] will be moved to next > alpha, so pleas don't waiting for it. > > In the same time SQL API: Examples [2] already done and merged to alpha 5 > branch. > > [1] https://issues.apache.org/jira/browse/IGNITE-16963 > [2] https://issues.apache.org/jira/browse/IGNITE-17088 > > пн, 6 июн. 2022 г. в 22:52, Andrey Gura : > > > Igniters, > > > > ignite-3.0.0-alpha5 release branch has been created. But the following > > issues are still in progress: > > > > Data rebalancing > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > SQL API: Add batched DML queries support. > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > SQL API: Examples. > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > Please, make sure these commits will be merged to the main and to the > > release branch. > > > > Thanks! > > > > On Mon, Jun 6, 2022 at 6:02 PM Aleksandr Pakhomov > > wrote: > > > > > > Hi Andrey, > > > > > > As for CLI MVP, the planned timeline is today till 21:00. > > > Probably, will be ready in an hour. Just waiting for CI build. > > > > > > Best regards, > > > Aleksandr > > > > > > > On 6 Jun 2022, at 17:56, Andrey Gura wrote: > > > > > > > > Igniters, > > > > > > > > our release schedule has shifted a bit. But it is time for a code > > > > freeze and a new branch creation. > > > > > > > > The following issues is still in progress (not an issues status, but > > > > work state): > > > > > > > > Data rebalancing > > > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > > > > > CLI MVP > > > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > > > > > SQL API: Implement query metadata > > > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > > > > > SQL API: Add batched DML queries support. > > > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > > > > > SQL API: Examples. > > > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > > > > > Please, give some planned timelines for these issues. I would like to > > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > > > Otherwise, extra steps will be required to include the PR's to the > > > > release branch. > > > > > > > > Thanks! > > > > > > > > -- > Живи с улыбкой! :D
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Seems SQL API: Add batched DML queries support [1] will be moved to next alpha, so pleas don't waiting for it. In the same time SQL API: Examples [2] already done and merged to alpha 5 branch. [1] https://issues.apache.org/jira/browse/IGNITE-16963 [2] https://issues.apache.org/jira/browse/IGNITE-17088 пн, 6 июн. 2022 г. в 22:52, Andrey Gura : > Igniters, > > ignite-3.0.0-alpha5 release branch has been created. But the following > issues are still in progress: > > Data rebalancing > https://issues.apache.org/jira/browse/IGNITE-14209 > > SQL API: Add batched DML queries support. > https://issues.apache.org/jira/browse/IGNITE-16963 > > SQL API: Examples. > https://issues.apache.org/jira/browse/IGNITE-17088 > > Please, make sure these commits will be merged to the main and to the > release branch. > > Thanks! > > On Mon, Jun 6, 2022 at 6:02 PM Aleksandr Pakhomov > wrote: > > > > Hi Andrey, > > > > As for CLI MVP, the planned timeline is today till 21:00. > > Probably, will be ready in an hour. Just waiting for CI build. > > > > Best regards, > > Aleksandr > > > > > On 6 Jun 2022, at 17:56, Andrey Gura wrote: > > > > > > Igniters, > > > > > > our release schedule has shifted a bit. But it is time for a code > > > freeze and a new branch creation. > > > > > > The following issues is still in progress (not an issues status, but > > > work state): > > > > > > Data rebalancing > > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > > > CLI MVP > > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > > > SQL API: Implement query metadata > > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > > > SQL API: Add batched DML queries support. > > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > > > SQL API: Examples. > > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > > > Please, give some planned timelines for these issues. I would like to > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > > Otherwise, extra steps will be required to include the PR's to the > > > release branch. > > > > > > Thanks! > > > -- Живи с улыбкой! :D
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Pavel, The issue is targeted to the alpha5 release. On Wed, Jun 8, 2022 at 11:13 AM Pavel Tupitsyn wrote: > > Igniters, I'd like to include the following ticket as well: > IGNITE-17057 Thin 3.0: Implement synchronous SQL API for java thin client > [1] > > Would be great to have the same API available in server and client modes. > It'll be in main in a couple hours. > > [1] https://issues.apache.org/jira/browse/IGNITE-17057 > > On Wed, Jun 8, 2022 at 9:27 AM Андрей Хитрин > wrote: > > > Looks reasonable to me. IGNITE-17129 could wait for the next release. Thank > > you! > > > > вт, 7 июн. 2022 г. в 20:05, Andrey Gura : > > > > > Andrey, > > > > > > while IGNITE-17128 is okay just because it demonstrates some > > > functionality, IGNITE-17129 doesn't look critical and could be fixed > > > in some future release. WDYT? > > > > > > On Tue, Jun 7, 2022 at 5:58 PM Андрей Хитрин > > > wrote: > > > > > > > > Hello! Could you please add the following issues to the release? > > > > > > > > * https://issues.apache.org/jira/browse/IGNITE-17128: > > > > PersistentPageMemoryStorageExample cannot be run twice > > > > * https://issues.apache.org/jira/browse/IGNITE-17129: cli tool doesn't > > > > expand tilde in a config path > > > > > > > > пн, 6 июн. 2022 г. в 19:56, Andrey Gura : > > > > > > > > > Igniters, > > > > > > > > > > our release schedule has shifted a bit. But it is time for a code > > > > > freeze and a new branch creation. > > > > > > > > > > The following issues is still in progress (not an issues status, but > > > > > work state): > > > > > > > > > > Data rebalancing > > > > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > > > > > > > CLI MVP > > > > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > > > > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > > > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > > > > > > > SQL API: Implement query metadata > > > > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > > > > > > > SQL API: Add batched DML queries support. > > > > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > > > > > > > SQL API: Examples. > > > > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > > > > > > > Please, give some planned timelines for these issues. I would like to > > > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > > > > Otherwise, extra steps will be required to include the PR's to the > > > > > release branch. > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > -- > > > > Андрей Хитрин > > > > > > > > > -- > > Андрей Хитрин > >
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
On Wed, Jun 8, 2022 at 11:13 AM Pavel Tupitsyn wrote: > > Igniters, I'd like to include the following ticket as well: > IGNITE-17057 Thin 3.0: Implement synchronous SQL API for java thin client > [1] > > Would be great to have the same API available in server and client modes. > It'll be in main in a couple hours. > > [1] https://issues.apache.org/jira/browse/IGNITE-17057 > > On Wed, Jun 8, 2022 at 9:27 AM Андрей Хитрин > wrote: > > > Looks reasonable to me. IGNITE-17129 could wait for the next release. Thank > > you! > > > > вт, 7 июн. 2022 г. в 20:05, Andrey Gura : > > > > > Andrey, > > > > > > while IGNITE-17128 is okay just because it demonstrates some > > > functionality, IGNITE-17129 doesn't look critical and could be fixed > > > in some future release. WDYT? > > > > > > On Tue, Jun 7, 2022 at 5:58 PM Андрей Хитрин > > > wrote: > > > > > > > > Hello! Could you please add the following issues to the release? > > > > > > > > * https://issues.apache.org/jira/browse/IGNITE-17128: > > > > PersistentPageMemoryStorageExample cannot be run twice > > > > * https://issues.apache.org/jira/browse/IGNITE-17129: cli tool doesn't > > > > expand tilde in a config path > > > > > > > > пн, 6 июн. 2022 г. в 19:56, Andrey Gura : > > > > > > > > > Igniters, > > > > > > > > > > our release schedule has shifted a bit. But it is time for a code > > > > > freeze and a new branch creation. > > > > > > > > > > The following issues is still in progress (not an issues status, but > > > > > work state): > > > > > > > > > > Data rebalancing > > > > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > > > > > > > CLI MVP > > > > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > > > > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > > > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > > > > > > > SQL API: Implement query metadata > > > > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > > > > > > > SQL API: Add batched DML queries support. > > > > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > > > > > > > SQL API: Examples. > > > > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > > > > > > > Please, give some planned timelines for these issues. I would like to > > > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > > > > Otherwise, extra steps will be required to include the PR's to the > > > > > release branch. > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > -- > > > > Андрей Хитрин > > > > > > > > > -- > > Андрей Хитрин > >
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Igniters, I'd like to include the following ticket as well: IGNITE-17057 Thin 3.0: Implement synchronous SQL API for java thin client [1] Would be great to have the same API available in server and client modes. It'll be in main in a couple hours. [1] https://issues.apache.org/jira/browse/IGNITE-17057 On Wed, Jun 8, 2022 at 9:27 AM Андрей Хитрин wrote: > Looks reasonable to me. IGNITE-17129 could wait for the next release. Thank > you! > > вт, 7 июн. 2022 г. в 20:05, Andrey Gura : > > > Andrey, > > > > while IGNITE-17128 is okay just because it demonstrates some > > functionality, IGNITE-17129 doesn't look critical and could be fixed > > in some future release. WDYT? > > > > On Tue, Jun 7, 2022 at 5:58 PM Андрей Хитрин > > wrote: > > > > > > Hello! Could you please add the following issues to the release? > > > > > > * https://issues.apache.org/jira/browse/IGNITE-17128: > > > PersistentPageMemoryStorageExample cannot be run twice > > > * https://issues.apache.org/jira/browse/IGNITE-17129: cli tool doesn't > > > expand tilde in a config path > > > > > > пн, 6 июн. 2022 г. в 19:56, Andrey Gura : > > > > > > > Igniters, > > > > > > > > our release schedule has shifted a bit. But it is time for a code > > > > freeze and a new branch creation. > > > > > > > > The following issues is still in progress (not an issues status, but > > > > work state): > > > > > > > > Data rebalancing > > > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > > > > > CLI MVP > > > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > > > > > SQL API: Implement query metadata > > > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > > > > > SQL API: Add batched DML queries support. > > > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > > > > > SQL API: Examples. > > > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > > > > > Please, give some planned timelines for these issues. I would like to > > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > > > Otherwise, extra steps will be required to include the PR's to the > > > > release branch. > > > > > > > > Thanks! > > > > > > > > > > > > > -- > > > Андрей Хитрин > > > > > -- > Андрей Хитрин >
Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze
Looks reasonable to me. IGNITE-17129 could wait for the next release. Thank you! вт, 7 июн. 2022 г. в 20:05, Andrey Gura : > Andrey, > > while IGNITE-17128 is okay just because it demonstrates some > functionality, IGNITE-17129 doesn't look critical and could be fixed > in some future release. WDYT? > > On Tue, Jun 7, 2022 at 5:58 PM Андрей Хитрин > wrote: > > > > Hello! Could you please add the following issues to the release? > > > > * https://issues.apache.org/jira/browse/IGNITE-17128: > > PersistentPageMemoryStorageExample cannot be run twice > > * https://issues.apache.org/jira/browse/IGNITE-17129: cli tool doesn't > > expand tilde in a config path > > > > пн, 6 июн. 2022 г. в 19:56, Andrey Gura : > > > > > Igniters, > > > > > > our release schedule has shifted a bit. But it is time for a code > > > freeze and a new branch creation. > > > > > > The following issues is still in progress (not an issues status, but > > > work state): > > > > > > Data rebalancing > > > https://issues.apache.org/jira/browse/IGNITE-14209 > > > > > > CLI MVP > > > https://issues.apache.org/jira/browse/IGNITE-16971 > > > > > > [Native Persistence 3.0] End-to-end test for persistent PageMemory > > > https://issues.apache.org/jira/browse/IGNITE-17107 > > > > > > SQL API: Implement query metadata > > > https://issues.apache.org/jira/browse/IGNITE-16962 > > > > > > SQL API: Add batched DML queries support. > > > https://issues.apache.org/jira/browse/IGNITE-16963 > > > > > > SQL API: Examples. > > > https://issues.apache.org/jira/browse/IGNITE-17088 > > > > > > Please, give some planned timelines for these issues. I would like to > > > create the ignite-3.0.0-alpha5 branch today and announce Code Freeze. > > > Otherwise, extra steps will be required to include the PR's to the > > > release branch. > > > > > > Thanks! > > > > > > > > > -- > > Андрей Хитрин > -- Андрей Хитрин
