[jira] [Created] (IGNITE-22404) Remove deprecated SqlQuery from Spring Data Extension
Nusrat Shakarov created IGNITE-22404: Summary: Remove deprecated SqlQuery from Spring Data Extension Key: IGNITE-22404 URL: https://issues.apache.org/jira/browse/IGNITE-22404 Project: Ignite Issue Type: Improvement Reporter: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22352) Fix bean creation race in spring-ses-ext
Nusrat Shakarov created IGNITE-22352: Summary: Fix bean creation race in spring-ses-ext Key: IGNITE-22352 URL: https://issues.apache.org/jira/browse/IGNITE-22352 Project: Ignite Issue Type: Improvement Reporter: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22352) Fix bean creation race in spring-ses-ext
[ https://issues.apache.org/jira/browse/IGNITE-22352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22352: Assignee: Andrey Novikov > Fix bean creation race in spring-ses-ext > > > Key: IGNITE-22352 > URL: https://issues.apache.org/jira/browse/IGNITE-22352 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Assignee: Andrey Novikov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-22079) Add spring 6 support to spring-data extension
[ https://issues.apache.org/jira/browse/IGNITE-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov resolved IGNITE-22079. -- Resolution: Duplicate > Add spring 6 support to spring-data extension > - > > Key: IGNITE-22079 > URL: https://issues.apache.org/jira/browse/IGNITE-22079 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-22078) Add spring 6 support to spring-tx extension
[ https://issues.apache.org/jira/browse/IGNITE-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov resolved IGNITE-22078. -- Resolution: Duplicate > Add spring 6 support to spring-tx extension > --- > > Key: IGNITE-22078 > URL: https://issues.apache.org/jira/browse/IGNITE-22078 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22102) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22102: Assignee: Nusrat Shakarov > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > Upgrade the following extensions: > * ignite-spring-cache-ext > * ignite-spring-data-ext > * ignite-spring-tx-ext -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22102) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22102: - Description: Upgrade the following extensions: * ignite-spring-cache-ext * ignite-spring-data-ext * ignite-spring-tx-ext was:Add spring 6 su > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > > Upgrade the following extensions: > * ignite-spring-cache-ext > * ignite-spring-data-ext > * ignite-spring-tx-ext -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22102) Add spring 6 support to spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22102: - Summary: Add spring 6 support to spring extensions (was: Add spring 6 support to spring-cache extension) > Add spring 6 support to spring extensions > - > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22102) Add spring 6 support to spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22102: - Description: Add spring 6 su > Add spring 6 support to spring extensions > - > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > > Add spring 6 su -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22102) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22102: - Summary: Upgrade ignite spring extensions to spring 6 (was: Update ignite spring extensions to spring 6) > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > > Add spring 6 su -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22102) Update ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22102: - Summary: Update ignite spring extensions to spring 6 (was: Add spring 6 support to spring extensions) > Update ignite spring extensions to spring 6 > --- > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > > Add spring 6 su -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22311) Fix checkstyle in spring-ses-ext
[ https://issues.apache.org/jira/browse/IGNITE-22311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22311: Assignee: Nusrat Shakarov > Fix checkstyle in spring-ses-ext > > > Key: IGNITE-22311 > URL: https://issues.apache.org/jira/browse/IGNITE-22311 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22311) Fix checkstyle in spring-ses-ext
Nusrat Shakarov created IGNITE-22311: Summary: Fix checkstyle in spring-ses-ext Key: IGNITE-22311 URL: https://issues.apache.org/jira/browse/IGNITE-22311 Project: Ignite Issue Type: Improvement Reporter: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which currently don't work in the spring 6 environment(basically, where the API is broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. We should use the lowest target possible. # If the spring module don't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module is used. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. was: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which currently don't work in the spring 6 environment(basically, where the API is broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. We should use the lowest target possible. # If the spring module don't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring Boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications because extensions are based on Spring 5. > Most of them
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which currently don't work in the spring 6 environment(basically, where the API is broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. We should use the lowest target possible. # If the spring module don't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. was: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which currently don't work in the spring 6 environment(basically, where the API is broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. We should use the lowest target possible. # If the spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring Boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications because extensions are based on Spring 5. > Most of them
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which currently don't work in the spring 6 environment(basically, where the API is broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. We should use the lowest target possible. # If the spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. was: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which currently don't work in the spring 6 environment(basically, where the API is broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If the spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring Boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications because extensions are based on Spring 5. > Most of them should work fine in Spring 6 apps, but we may
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which won't work in the spring 6 environment(basically, where the API was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If the spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. was: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which won't work in the spring 6 environment(basically, where the API was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If the spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring Boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications because extensions are based on Spring 5. > Most of them should work fine in Spring 6 apps, but we may find ourselves on > thin ice. > For some
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which currently don't work in the spring 6 environment(basically, where the API is broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If the spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. was: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which won't work in the spring 6 environment(basically, where the API was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If the spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring Boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications because extensions are based on Spring 5. > Most of them should work fine in Spring 6 apps, but we may find ourselves on > thin ice. > For some spring
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring Boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications because extensions are based on Spring 5. Most of them should work fine in Spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring-based ignite extensions to spring 6. The upgrade will affect modules which won't work in the spring 6 environment(basically, where the API was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. The project will support both options, spring 6 modules will be enabled only when JDK 17 is used. The main build will be with JDK 17 because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If the spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to the compatibility test, the module should be built only with JDK 17, otherwise, tests will fail. But maven.compiler.release can be 8. # For updated modules use a new versioning approach. Use the same major and minor for spring extension as the corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, the spring-session-ext version should be 3.2.x, where x is the revision number. # If we update the module to spring 6 and we need a fix for the previous module version(which is based on spring 5), we can apply the fix to the master first, create a release branch(checkout from the previous spring 5 release) and cherry-pick fix. was: This epic is about spring 6 support for ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used. The main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, the module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. # If we update module to spring 6 and we need fix for previous module version(which is based on spring 5), we can apply fix to master first, create release branch(checkout from previous spring 5 release) and cherry pick fix. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring Boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications because extensions are based on Spring 5. > Most of them should work fine in Spring 6 apps, but we may find ourselves on > thin ice with this approach. > For some spring modules
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used. The main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, the module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. # If we update module to spring 6 and we need fix for previous module version(which is based on spring 5), we can apply fix to master first, create release branch(checkout from previous spring 5 release) and cherry pick fix. was: This epic is about spring 6 support for ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used. The main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used. The main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This epic is about spring 6 support for ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > # Add ignite extensions
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This epic is about spring 6 support for ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support for ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This epic is about spring 6 support for ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > #
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support for ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support for ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > #
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. But maven.compiler.release can be 8. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > # Add ignite extensions build on TC with
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext). If spring 6 is added to compatibility test, this module should be build only with JDK 17, otherwise tests will fail. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > # Add ignite extensions build on TC with JDK 17. JDK 8 build option still > will be available. Project will support both options, sprint 6 modules will > be enabled only when jdk 17 is used, so in
[jira] [Assigned] (IGNITE-22102) Add spring 6 support to spring-cache extension
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22102: Assignee: (was: Nusrat Shakarov) > Add spring 6 support to spring-cache extension > -- > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22103) Add spring 6 support to spring autoconfiguration extension
[ https://issues.apache.org/jira/browse/IGNITE-22103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22103: Assignee: (was: Nusrat Shakarov) > Add spring 6 support to spring autoconfiguration extension > -- > > Key: IGNITE-22103 > URL: https://issues.apache.org/jira/browse/IGNITE-22103 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22078) Add spring 6 support to spring-tx extension
[ https://issues.apache.org/jira/browse/IGNITE-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22078: Assignee: (was: Nusrat Shakarov) > Add spring 6 support to spring-tx extension > --- > > Key: IGNITE-22078 > URL: https://issues.apache.org/jira/browse/IGNITE-22078 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22079) Add spring 6 support to spring-data extension
[ https://issues.apache.org/jira/browse/IGNITE-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22079: Assignee: (was: Nusrat Shakarov) > Add spring 6 support to spring-data extension > - > > Key: IGNITE-22079 > URL: https://issues.apache.org/jira/browse/IGNITE-22079 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Summary: Spring 6 support for ignite spring extensions (was: Upgrade ignite spring extensions to spring 6) > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > # Add ignite extensions build on TC with JDK 17. JDK 8 build option still > will be available. Project will support both options, sprint 6 modules will > be enabled only when jdk 17 is used, so in the end the main build will be > with jdk 17, because it covers all modules. > # Use maven.compiler.release=8 for parent pom. > # If spring module won't work in spring 6 env, upgrade it with spring 6 > dependencies and set maven.compiler.release=17. > # Otherwise, make sure that spring 6 is covered with compatibility tests(we > have such at least for cache-ext and tx-ext. > # For updated modules use new versioning approach. Use the same major and > minor for spring extension as corresponding spring module uses. For example, > If spring-session-core is updated to 3.2.2, spring-session-ext version should > be 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22096) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options, sprint 6 modules will be enabled only when jdk 17 is used, so in the end the main build will be with jdk 17, because it covers all modules. # Use maven.compiler.release=8 for parent pom. # If spring module won't work in spring 6 env, upgrade it with spring 6 dependencies and set maven.compiler.release=17. # Otherwise, make sure that spring 6 is covered with compatibility tests(we have such at least for cache-ext and tx-ext. # For updated modules use new versioning approach. Use the same major and minor for spring extension as corresponding spring module uses. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options. # Use maven.compiler.release=8, for all modules except spring based modules # Upgrade spring modules(where it is necessary) to spring 6 and maven.compiler.release=17 # Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > # Add ignite extensions build on TC with JDK 17. JDK 8 build option still > will be available. Project will support both options, sprint 6 modules will > be enabled only when jdk 17 is used, so in the end the main build will be > with jdk 17, because it covers all modules. > # Use maven.compiler.release=8 for parent pom. > # If spring module won't work in spring 6 env, upgrade it with spring 6 > dependencies and set maven.compiler.release=17. > # Otherwise, make sure that spring 6 is covered with compatibility tests(we > have such at least for cache-ext and tx-ext. > # For updated modules use
[jira] [Updated] (IGNITE-22096) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Add ignite extensions build on TC with JDK 17. JDK 8 build option still will be available. Project will support both options. # Use maven.compiler.release=8, for all modules except spring based modules # Upgrade spring modules(where it is necessary) to spring 6 and maven.compiler.release=17 # Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Build ignite extensions using JDK 17 (JDK 8 build option still will be available for patch releases) # Use maven.compiler.release=8, for all modules except spring based modules # Upgrade spring modules(where it is necessary) to spring 6 and maven.compiler.release=17 # Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > # Add ignite extensions build on TC with JDK 17. JDK 8 build option still > will be available. Project will support both options. > # Use maven.compiler.release=8, for all modules except spring based modules > # Upgrade spring modules(where it is necessary) to spring 6 and > maven.compiler.release=17 > # Use new versioning approach. Use the same major and minor for spring > extension as corresponding spring module used. For example, If > spring-session-core is updated to 3.2.2, spring-session-ext version should be > 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22096) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: # Build ignite extensions using JDK 17 (JDK 8 build option still will be available for patch releases) # Use maven.compiler.release=8, for all modules except spring based modules # Upgrade spring modules(where it is necessary) to spring 6 and maven.compiler.release=17 # Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be available for patch releases) 2. Use maven.compiler.release=8, for all modules except spring based modules 3. Upgrade spring modules(where it is necessary) to spring 6 and maven.compiler.release=17 4. Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > # Build ignite extensions using JDK 17 (JDK 8 build option still will be > available for patch releases) > # Use maven.compiler.release=8, for all modules except spring based modules > # Upgrade spring modules(where it is necessary) to spring 6 and > maven.compiler.release=17 > # Use new versioning approach. Use the same major and minor for spring > extension as corresponding spring module used. For example, If > spring-session-core is updated to 3.2.2, spring-session-ext version should be > 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22096) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. The proposal is to upgrade spring based ignite extensions to spring 6. The upgrade will affect modules which won't work in spring 6 environment(basically, where api was broken). Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be available for patch releases) 2. Use maven.compiler.release=8, for all modules except spring based modules 3. Upgrade spring modules(where it is necessary) to spring 6 and maven.compiler.release=17 4. Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. Considering that, the proposal is to upgrade all spring based ignite extensions to spring 6. Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be available for patch releases) 2. Use maven.compiler.release=8, for all modules except spring based modules 3. Upgrade spring modules(where it is necessary) to spring 6 and maven.compiler.release=17 4. Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > The proposal is to upgrade spring based ignite extensions to spring 6. The > upgrade will affect modules which won't work in spring 6 > environment(basically, where api was broken). > Taking into consideration that spring 6 comes with JDK 17+ baseline the plan > is the following: > 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be > available for patch releases) > 2. Use maven.compiler.release=8, for all modules except spring based modules > 3. Upgrade spring modules(where it is necessary) to spring 6 and > maven.compiler.release=17 > 4. Use new versioning approach. Use the same major and minor for spring > extension as corresponding spring module used. For example, If > spring-session-core is updated to > 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22096) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. Considering that, the proposal is to upgrade all spring based ignite extensions to spring 6. Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be available for patch releases) 2. Use maven.compiler.release=8, for all modules except spring based modules 3. Upgrade spring modules(where it is necessary) to spring 6 and maven.compiler.release=17 4. Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. Considering that, the proposal is to upgrade all spring based ignite extensions to spring 6. Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be available for patch releases) 2. Use maven.compiler.release=8, for all modules except spring based modules 3. Upgrade spring modules to spring 6 and maven.compiler.release=17 4. Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > Considering that, the proposal is to upgrade all spring based ignite > extensions to spring 6. Taking into consideration that spring 6 comes with > JDK 17+ baseline the plan is the following: > 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be > available for patch releases) > 2. Use maven.compiler.release=8, for all modules except spring based modules > 3. Upgrade spring modules(where it is necessary) to spring 6 and > maven.compiler.release=17 > 4. Use new versioning approach. Use the same major and minor for spring > extension as corresponding spring module used. For example, If > spring-session-core is updated to > 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22103) Add spring 6 support to spring autoconfiguration extension
Nusrat Shakarov created IGNITE-22103: Summary: Add spring 6 support to spring autoconfiguration extension Key: IGNITE-22103 URL: https://issues.apache.org/jira/browse/IGNITE-22103 Project: Ignite Issue Type: Improvement Reporter: Nusrat Shakarov Assignee: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22102) Add spring 6 support to spring-cache extension
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22102: - Summary: Add spring 6 support to spring-cache extension (was: Upgrade spring-cache and autoconfiguration extensions to spring 6) > Add spring 6 support to spring-cache extension > -- > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22096) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Description: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. Actually, most of them should work fine in spring 6 apps, but we may find ourselves on thin ice with this approach. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. Considering that, the proposal is to upgrade all spring based ignite extensions to spring 6. Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be available for patch releases) 2. Use maven.compiler.release=8, for all modules except spring based modules 3. Upgrade spring modules to spring 6 and maven.compiler.release=17 4. Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. was: This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. Considering that, the proposal is to upgrade all spring based ignite extensions to spring 6. Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: 1. Build ignite extensions using JDK 17 2. Use maven.compiler.release=8, for all modules except spring based modules 3. Upgrade spring modules to spring 6 and maven.compiler.release=17 4. Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > Actually, most of them should work fine in spring 6 apps, but we may find > ourselves on thin ice with this approach. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > Considering that, the proposal is to upgrade all spring based ignite > extensions to spring 6. Taking into consideration that spring 6 comes with > JDK 17+ baseline the plan is the following: > 1. Build ignite extensions using JDK 17 (JDK 8 build option still will be > available for patch releases) > 2. Use maven.compiler.release=8, for all modules except spring based modules > 3. Upgrade spring modules to spring 6 and maven.compiler.release=17 > 4. Use new versioning approach. Use the same major and minor for spring > extension as corresponding spring module used. For example, If > spring-session-core is updated to > 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22096) Upgrade ignite spring extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22096: - Summary: Upgrade ignite spring extensions to spring 6 (was: Spring 6 support for ignite spring extensions) > Upgrade ignite spring extensions to spring 6 > > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > Considering that, the proposal is to upgrade all spring based ignite > extensions to spring 6. Taking into consideration that spring 6 comes with > JDK 17+ baseline the plan is the following: > 1. Build ignite extensions using JDK 17 > 2. Use maven.compiler.release=8, for all modules except spring based modules > 3. Upgrade spring modules to spring 6 and maven.compiler.release=17 > 4. Use new versioning approach. Use the same major and minor for spring > extension as corresponding spring module used. For example, If > spring-session-core is updated to > 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22102) Upgrade spring-cache and autoconfiguration extensions to spring 6
[ https://issues.apache.org/jira/browse/IGNITE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22102: - Summary: Upgrade spring-cache and autoconfiguration extensions to spring 6 (was: Add spring 6 support to spring-cache and autoconfiguration extensions) > Upgrade spring-cache and autoconfiguration extensions to spring 6 > - > > Key: IGNITE-22102 > URL: https://issues.apache.org/jira/browse/IGNITE-22102 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22102) Add spring 6 support to spring-cache and autoconfiguration extensions
Nusrat Shakarov created IGNITE-22102: Summary: Add spring 6 support to spring-cache and autoconfiguration extensions Key: IGNITE-22102 URL: https://issues.apache.org/jira/browse/IGNITE-22102 Project: Ignite Issue Type: Improvement Reporter: Nusrat Shakarov Assignee: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22096) Spring 6 support for ignite spring extensions
[ https://issues.apache.org/jira/browse/IGNITE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22096: Assignee: Nusrat Shakarov > Spring 6 support for ignite spring extensions > - > > Key: IGNITE-22096 > URL: https://issues.apache.org/jira/browse/IGNITE-22096 > Project: Ignite > Issue Type: Epic >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > > This is epic about spring 6 support in ignite extensions. > Spring boot 3 and Spring 6 users may have difficulties using ignite spring > extensions in their applications, because extensions based on spring 5. > For some spring modules like spring-data-commons and spring-session-core, > Spring has finished spring 5 support in Nov 2023. For other modules(and > spring-core) support ends in Aug 2024. > Considering that, the proposal is to upgrade all spring based ignite > extensions to spring 6. Taking into consideration that spring 6 comes with > JDK 17+ baseline the plan is the following: > 1. Build ignite extensions using JDK 17 > 2. Use maven.compiler.release=8, for all modules except spring based modules > 3. Upgrade spring modules to spring 6 and maven.compiler.release=17 > 4. Use new versioning approach. Use the same major and minor for spring > extension as corresponding spring module used. For example, If > spring-session-core is updated to > 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22077) Add spring 6 support to spring-session extension
[ https://issues.apache.org/jira/browse/IGNITE-22077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22077: Assignee: Nusrat Shakarov > Add spring 6 support to spring-session extension > > > Key: IGNITE-22077 > URL: https://issues.apache.org/jira/browse/IGNITE-22077 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22079) Add spring 6 support to spring-data extension
[ https://issues.apache.org/jira/browse/IGNITE-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22079: Assignee: Nusrat Shakarov > Add spring 6 support to spring-data extension > - > > Key: IGNITE-22079 > URL: https://issues.apache.org/jira/browse/IGNITE-22079 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22078) Add spring 6 support to spring-tx extension
[ https://issues.apache.org/jira/browse/IGNITE-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov reassigned IGNITE-22078: Assignee: Nusrat Shakarov > Add spring 6 support to spring-tx extension > --- > > Key: IGNITE-22078 > URL: https://issues.apache.org/jira/browse/IGNITE-22078 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Assignee: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22079) Add spring 6 support to spring-data extension
[ https://issues.apache.org/jira/browse/IGNITE-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22079: - Epic Link: IGNITE-22096 > Add spring 6 support to spring-data extension > - > > Key: IGNITE-22079 > URL: https://issues.apache.org/jira/browse/IGNITE-22079 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22078) Add spring 6 support to spring-tx extension
[ https://issues.apache.org/jira/browse/IGNITE-22078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22078: - Epic Link: IGNITE-22096 > Add spring 6 support to spring-tx extension > --- > > Key: IGNITE-22078 > URL: https://issues.apache.org/jira/browse/IGNITE-22078 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22077) Add spring 6 support to spring-session extension
[ https://issues.apache.org/jira/browse/IGNITE-22077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-22077: - Epic Link: IGNITE-22096 > Add spring 6 support to spring-session extension > > > Key: IGNITE-22077 > URL: https://issues.apache.org/jira/browse/IGNITE-22077 > Project: Ignite > Issue Type: Improvement >Reporter: Nusrat Shakarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22096) Spring 6 support for ignite spring extensions
Nusrat Shakarov created IGNITE-22096: Summary: Spring 6 support for ignite spring extensions Key: IGNITE-22096 URL: https://issues.apache.org/jira/browse/IGNITE-22096 Project: Ignite Issue Type: Epic Reporter: Nusrat Shakarov This is epic about spring 6 support in ignite extensions. Spring boot 3 and Spring 6 users may have difficulties using ignite spring extensions in their applications, because extensions based on spring 5. For some spring modules like spring-data-commons and spring-session-core, Spring has finished spring 5 support in Nov 2023. For other modules(and spring-core) support ends in Aug 2024. Considering that, the proposal is to upgrade all spring based ignite extensions to spring 6. Taking into consideration that spring 6 comes with JDK 17+ baseline the plan is the following: 1. Build ignite extensions using JDK 17 2. Use maven.compiler.release=8, for all modules except spring based modules 3. Upgrade spring modules to spring 6 and maven.compiler.release=17 4. Use new versioning approach. Use the same major and minor for spring extension as corresponding spring module used. For example, If spring-session-core is updated to 3.2.2, spring-session-ext version should be 3.2.x, where x is revision number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22079) Add spring 6 support to spring-data extension
Nusrat Shakarov created IGNITE-22079: Summary: Add spring 6 support to spring-data extension Key: IGNITE-22079 URL: https://issues.apache.org/jira/browse/IGNITE-22079 Project: Ignite Issue Type: Improvement Reporter: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22078) Add spring 6 support to spring-tx extension
Nusrat Shakarov created IGNITE-22078: Summary: Add spring 6 support to spring-tx extension Key: IGNITE-22078 URL: https://issues.apache.org/jira/browse/IGNITE-22078 Project: Ignite Issue Type: Improvement Reporter: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22077) Add spring 6 support to spring-session extension
Nusrat Shakarov created IGNITE-22077: Summary: Add spring 6 support to spring-session extension Key: IGNITE-22077 URL: https://issues.apache.org/jira/browse/IGNITE-22077 Project: Ignite Issue Type: Improvement Reporter: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-18054) Implement sql query free memory metric in percents
[ https://issues.apache.org/jira/browse/IGNITE-18054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov resolved IGNITE-18054. -- Resolution: Won't Do > Implement sql query free memory metric in percents > -- > > Key: IGNITE-18054 > URL: https://issues.apache.org/jira/browse/IGNITE-18054 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Nusrat Shakarov >Priority: Major > > There is a need to have sql query free memory in percent. > In some cases the absolute value of freeMem metric does not give a clear > understanding of potential problems. > The proposal is to implement a new metric - freeMemPercentage - based on > freeMem and maxMem metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18054) Implement sql query free memory metric in percents
[ https://issues.apache.org/jira/browse/IGNITE-18054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-18054: - Description: There is a need to have sql query free memory in percent. In some cases the absolute value of freeMem metric does not give a clear understanding of potential problems. The proposal is to implement a new metric - freeMemPercentage - based on freeMem and maxMem metrics. was: There is a need to have sql query free memory in percent. In some cases the absolute value of freeMem metric does not give a clear understanding of potential problems. The proposal is to create a new metric - freeMemPercentage - based on freeMem and maxMem metrics. > Implement sql query free memory metric in percents > -- > > Key: IGNITE-18054 > URL: https://issues.apache.org/jira/browse/IGNITE-18054 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Nusrat Shakarov >Priority: Major > > There is a need to have sql query free memory in percent. > In some cases the absolute value of freeMem metric does not give a clear > understanding of potential problems. > The proposal is to implement a new metric - freeMemPercentage - based on > freeMem and maxMem metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18054) Implement sql query free memory metric in percents
[ https://issues.apache.org/jira/browse/IGNITE-18054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-18054: - Description: There is a need to have sql query free memory in percent. In some cases the absolute value of freeMem metric does not give a clear understanding of potential problems. The proposal is to create a new metric - freeMemPercentage - based on freeMem and maxMem metrics. was:There is a need to have sql query free memory in percent. > Implement sql query free memory metric in percents > -- > > Key: IGNITE-18054 > URL: https://issues.apache.org/jira/browse/IGNITE-18054 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Nusrat Shakarov >Priority: Major > > There is a need to have sql query free memory in percent. > In some cases the absolute value of freeMem metric does not give a clear > understanding of potential problems. > The proposal is to create a new metric - freeMemPercentage - based on freeMem > and maxMem metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18054) Implement sql query free memory metric in percents
[ https://issues.apache.org/jira/browse/IGNITE-18054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nusrat Shakarov updated IGNITE-18054: - Description: There is a need to have sql query free memory in percent. > Implement sql query free memory metric in percents > -- > > Key: IGNITE-18054 > URL: https://issues.apache.org/jira/browse/IGNITE-18054 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Nusrat Shakarov >Priority: Major > > There is a need to have sql query free memory in percent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18054) Implement sql query free memory metric in percents
Nusrat Shakarov created IGNITE-18054: Summary: Implement sql query free memory metric in percents Key: IGNITE-18054 URL: https://issues.apache.org/jira/browse/IGNITE-18054 Project: Ignite Issue Type: Improvement Components: sql Reporter: Nusrat Shakarov -- This message was sent by Atlassian Jira (v8.20.10#820010)