[jira] [Resolved] (IGNITE-21889) Remove MVCC code from DataPageIO class
[ https://issues.apache.org/jira/browse/IGNITE-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julia Bakulina resolved IGNITE-21889. - Resolution: Duplicate > Remove MVCC code from DataPageIO class > -- > > Key: IGNITE-21889 > URL: https://issues.apache.org/jira/browse/IGNITE-21889 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Major > Labels: ise > > Delete TxState -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22104) Documentation of Custom Metrics
[ https://issues.apache.org/jira/browse/IGNITE-22104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-22104: -- Labels: ise (was: ) > Documentation of Custom Metrics > --- > > Key: IGNITE-22104 > URL: https://issues.apache.org/jira/browse/IGNITE-22104 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.17 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Labels: ise > > New Custom Metric feature should be documented. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22104) Documentation of Custom Metrics
[ https://issues.apache.org/jira/browse/IGNITE-22104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-22104: -- Component/s: documentation > Documentation of Custom Metrics > --- > > Key: IGNITE-22104 > URL: https://issues.apache.org/jira/browse/IGNITE-22104 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.17 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > New Custom Metric feature should be documented. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22104) Documentation of Custom Metrics
Vladimir Steshin created IGNITE-22104: - Summary: Documentation of Custom Metrics Key: IGNITE-22104 URL: https://issues.apache.org/jira/browse/IGNITE-22104 Project: Ignite Issue Type: Task Reporter: Vladimir Steshin Assignee: Vladimir Steshin New Custom Metric feature should be documented. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22104) Documentation of Custom Metrics
[ https://issues.apache.org/jira/browse/IGNITE-22104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-22104: -- Affects Version/s: 2.17 > Documentation of Custom Metrics > --- > > Key: IGNITE-22104 > URL: https://issues.apache.org/jira/browse/IGNITE-22104 > Project: Ignite > Issue Type: Task >Affects Versions: 2.17 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > New Custom Metric feature should be documented. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22104) Documentation of Custom Metrics
[ https://issues.apache.org/jira/browse/IGNITE-22104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-22104: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Documentation of Custom Metrics > --- > > Key: IGNITE-22104 > URL: https://issues.apache.org/jira/browse/IGNITE-22104 > Project: Ignite > Issue Type: Task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > New Custom Metric feature should be documented. -- 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 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-21835) MVCC code: final cleanup
[ https://issues.apache.org/jira/browse/IGNITE-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-21835: --- Summary: MVCC code: final cleanup (was: Cleanup MvccUtils and enum RowData) > MVCC code: final cleanup > > > Key: IGNITE-21835 > URL: https://issues.apache.org/jira/browse/IGNITE-21835 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Ilya Shishkov >Priority: Major > Labels: ise > Time Spent: 1h > Remaining Estimate: 0h > > To cleanup MvccUtils and enum RowData: > * LINK_ONLY > * LINK_WITH_HEADER > * NO_KEY_WTH_HINTS. > Delete MVCC classes: > * MvccVersion > * MvccVersionImpl > * MvccUpdateVersionAware. > The remaining MvccUtils.tx(..) methods will be removed in IGNITE-21345 -- 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] [Commented] (IGNITE-21345) TxState and MvccSnapshot removal
[ https://issues.apache.org/jira/browse/IGNITE-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840550#comment-17840550 ] Ilya Shishkov commented on IGNITE-21345: [~av], thank you a lot for the review! > TxState and MvccSnapshot removal > > > Key: IGNITE-21345 > URL: https://issues.apache.org/jira/browse/IGNITE-21345 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > Remove o.a.i.internal.processors.cache.mvcc.txlog.TxState (as a continuation > of the IGNITE-21130) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17996) Strange behavior of SQL CASE expression
[
https://issues.apache.org/jira/browse/IGNITE-17996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin resolved IGNITE-17996.
-
Resolution: Not A Bug
> Strange behavior of SQL CASE expression
> ---
>
> Key: IGNITE-17996
> URL: https://issues.apache.org/jira/browse/IGNITE-17996
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-beta1
>Reporter: Andrey Khitrin
>Priority: Major
> Labels: ignite-3
>
> I observe strange behavior in the next scenario:
>
> {code:java}
> sql-cli> create table xx (f1 int primary key);
> Updated 0 rows.
> sql-cli> insert into xx values (1);
> Updated 1 rows.
> sql-cli> insert into xx values (2);
> Updated 1 rows.
> sql-cli> select f1, case when f1 < 2 then 'foo' else 'barbar' end as s,
> length(case when f1 < 2 then 'foo' else 'barbar' end) as ls from xx;
> ╔╤╤╗
> ║ F1 │ S │ LS ║
> ╠╪╪╣
> ║ 2 │ barbar │ 6 ║
> ╟┼┼╢
> ║ 1 │ foo │ 6 ║
> ╚╧╧╝
> {code}
> I expect `CASE` to return 'foo' value, but de-facto it returns 'foo '
> ('foo' with 3 whitespaces at the end). Seems like this should be fixed.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-17997) Whitespaces at the end are ignored during string comparison
[
https://issues.apache.org/jira/browse/IGNITE-17997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Khitrin resolved IGNITE-17997.
-
Resolution: Not A Bug
> Whitespaces at the end are ignored during string comparison
> ---
>
> Key: IGNITE-17997
> URL: https://issues.apache.org/jira/browse/IGNITE-17997
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Andrey Khitrin
>Priority: Major
> Labels: ignite-3
>
> In 3.0.0-Beta-1:
> {code:java}
> sql-cli> select 'a' = 'a' as t1, 'a' = 'b' as t2, 'a' = 'a ' as t3, 'a' = '
> a' as t4;
> ╔══╤═══╤══╤═══╗
> ║ T1 │ T2 │ T3 │ T4 ║
> ╠══╪═══╪══╪═══╣
> ║ true │ false │ true │ false ║
> ╚══╧═══╧══╧═══╝
> {code}
> Tests T1, T2, and T4 show correct behavior. But in test T2 we see that string
> 'a' is considered being equal to string 'a ' (same string but with
> arbitrary amount of whitespaces at the end). This is incorrect behavior.
> This issue may have the same nature as IGNITE-17996, but it's just a
> hypothesis.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22101) Performance drop for thin client requests
[ https://issues.apache.org/jira/browse/IGNITE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-22101: --- Description: After IGNITE-21183 there is performance drop for thin client transactional operations up to 38%: !perf_drop.png|width=1083,height=168! was: After IGNITE-21183 there is performance drop for thin client transactional operations up to 38%: !image-2024-04-24-18-40-52-125.png|width=884,height=137! > Performance drop for thin client requests > - > > Key: IGNITE-22101 > URL: https://issues.apache.org/jira/browse/IGNITE-22101 > Project: Ignite > Issue Type: Bug >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: ise > Attachments: perf_drop.png > > > After IGNITE-21183 there is performance drop for thin client transactional > operations up to 38%: > !perf_drop.png|width=1083,height=168! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22101) Performance drop for thin client requests
[ https://issues.apache.org/jira/browse/IGNITE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-22101: --- Attachment: (was: image-2024-04-24-18-40-52-125.png) > Performance drop for thin client requests > - > > Key: IGNITE-22101 > URL: https://issues.apache.org/jira/browse/IGNITE-22101 > Project: Ignite > Issue Type: Bug >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: ise > Attachments: perf_drop.png > > > After IGNITE-21183 there is performance drop for thin client transactional > operations up to 38%: > !image-2024-04-24-18-40-52-125.png|width=884,height=137! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22101) Performance drop for thin client requests
Aleksey Plekhanov created IGNITE-22101: -- Summary: Performance drop for thin client requests Key: IGNITE-22101 URL: https://issues.apache.org/jira/browse/IGNITE-22101 Project: Ignite Issue Type: Bug Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov Attachments: perf_drop.png After IGNITE-21183 there is performance drop for thin client transactional operations up to 38%: !image-2024-04-24-18-40-52-125.png|width=884,height=137! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-21830) Add logging of connection check for each address
[ https://issues.apache.org/jira/browse/IGNITE-21830 ] Maksim Davydov deleted comment on IGNITE-21830: - was (Author: JIRAUSER305006): PR url: https://github.com/apache/ignite/pull/11327 > Add logging of connection check for each address > > > Key: IGNITE-21830 > URL: https://issues.apache.org/jira/browse/IGNITE-21830 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Trivial > Labels: ise, newbie > Time Spent: 10m > Remaining Estimate: 0h > > Currently, exception thrown during checking of address is ignored [1]. It > would be useful to print message with connection check summary including each > address checking state and error message (if any). > # > https://github.com/apache/ignite/blob/7cd0c7a7d1150bbf6be6aae5efe80627a73757c0/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L7293 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21830) Add logging of connection check for each address
[ https://issues.apache.org/jira/browse/IGNITE-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840454#comment-17840454 ] Maksim Davydov commented on IGNITE-21830: - PR url: https://github.com/apache/ignite/pull/11327 > Add logging of connection check for each address > > > Key: IGNITE-21830 > URL: https://issues.apache.org/jira/browse/IGNITE-21830 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Shishkov >Assignee: Maksim Davydov >Priority: Trivial > Labels: ise, newbie > Time Spent: 10m > Remaining Estimate: 0h > > Currently, exception thrown during checking of address is ignored [1]. It > would be useful to print message with connection check summary including each > address checking state and error message (if any). > # > https://github.com/apache/ignite/blob/7cd0c7a7d1150bbf6be6aae5efe80627a73757c0/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L7293 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22100) Sql. Incorrect support of character set for CHAR data type
Iurii Gerzhedovich created IGNITE-22100:
---
Summary: Sql. Incorrect support of character set for CHAR data type
Key: IGNITE-22100
URL: https://issues.apache.org/jira/browse/IGNITE-22100
Project: Ignite
Issue Type: Improvement
Reporter: Iurii Gerzhedovich
Seems the character set doesn't apply to column type.
Need to investigate the reason and fix it
For example:
{code:java}
// create table with LATIN-1 charset column
CREATE TABLE t_latin1 (c1 CHARACTER(3) CHARACTER SET LATIN1);
// try to insert Unicode symbol into he table
INSERT INTO t_latin1 VALUES(''); -- no any error
// select from the table also return the value
SELECT * from t_latin1;
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21859) Causality token stays 0 for default zone
[
https://issues.apache.org/jira/browse/IGNITE-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-21859:
--
Fix Version/s: 3.0.0-beta2
> Causality token stays 0 for default zone
>
>
> Key: IGNITE-21859
> URL: https://issues.apache.org/jira/browse/IGNITE-21859
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-beta1
>Reporter: Ivan Zlenko
>Assignee: Konstantin Orlov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have a problem where if no alter or other action was performed on default
> zone causality token in CatalogZoneDescriptor will remain 0.
> It will cause an error on any attempt of rebalacing any tables in that zone:
> {code}
> [2024-03-27T14:27:22,231][ERROR][%icbt_tacwdws_0%rebalance-scheduler-18][DistributionZoneRebalanceEngine]
> Failed to update stable keys for tables [[TESTTABLE]]
> {code}
> If we will add stacktrace to output we will get following:
> {code}
> [2024-03-27T14:27:22,231][ERROR][%icbt_tacwdws_0%rebalance-scheduler-13][DistributionZoneRebalanceEngine]
> CATCH,
> java.lang.IllegalArgumentException: causalityToken must be greater then zero
> [causalityToken=0"
> at
> org.apache.ignite.internal.distributionzones.causalitydatanodes.CausalityDataNodesEngine.dataNodes(CausalityDataNodesEngine.java:139)
> ~[ignite-distribution-zones-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.distributionzones.DistributionZoneManager.dataNodes(DistributionZoneManager.java:324)
> ~[ignite-distribution-zones-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.distributionzones.rebalance.DistributionZoneRebalanceEngine.calculateAssignments(DistributionZoneRebalanceEngine.java:346)
> ~[ignite-distribution-zones-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.distributionzones.rebalance.RebalanceRaftGroupEventsListener.doStableKeySwitch(RebalanceRaftGroupEventsListener.java:408)
> ~[ignite-distribution-zones-9.0.127-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.distributionzones.rebalance.DistributionZoneRebalanceEngine$3.lambda$onUpdate$0(DistributionZoneRebalanceEngine.java:294)
> ~[ignite-distribution-zones-9.0.127-SNAPSHOT.jar:?]
> at java.base/java.util.HashMap.forEach(HashMap.java:1337) ~[?:?]
> at
> org.apache.ignite.internal.distributionzones.rebalance.DistributionZoneRebalanceEngine$3.lambda$onUpdate$1(DistributionZoneRebalanceEngine.java:293)
> ~[ignite-distribution-zones-9.0.127-SNAPSHOT.jar:?]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> [?:?]
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> [?:?]
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> [?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [?:?]
> at java.base/java.lang.Thread.run(Thread.java:829) [?:?]
> {code}
> The workaround is creating a zone and specifying this zone to table.
> Also wouldn't be a bad idea to print stacktrace for "Failed to update stable
> keys for tables" at least on DEBUG log level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22099) Delete TransactionDuplicateKeyException
[ https://issues.apache.org/jira/browse/IGNITE-22099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Nadyktov updated IGNITE-22099: - Description: Delete TransactionDuplicateKeyException which is unused after MVCC code removal (was: Delete TransactionSerializationException and TransactionAlreadyCompletedException that are unused after MVCC code removal) > Delete TransactionDuplicateKeyException > --- > > Key: IGNITE-22099 > URL: https://issues.apache.org/jira/browse/IGNITE-22099 > Project: Ignite > Issue Type: Sub-task >Reporter: Andrei Nadyktov >Assignee: Andrei Nadyktov >Priority: Trivial > Labels: ise, newbie > > Delete TransactionDuplicateKeyException which is unused after MVCC code > removal -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22099) Delete TransactionDuplicateKeyException
Andrei Nadyktov created IGNITE-22099: Summary: Delete TransactionDuplicateKeyException Key: IGNITE-22099 URL: https://issues.apache.org/jira/browse/IGNITE-22099 Project: Ignite Issue Type: Sub-task Reporter: Andrei Nadyktov Assignee: Andrei Nadyktov Delete TransactionSerializationException and TransactionAlreadyCompletedException that are unused after MVCC code removal -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22098) Sql. Internal error (NPE) during provide incorrect charset
Iurii Gerzhedovich created IGNITE-22098:
---
Summary: Sql. Internal error (NPE) during provide incorrect charset
Key: IGNITE-22098
URL: https://issues.apache.org/jira/browse/IGNITE-22098
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Iurii Gerzhedovich
In the case provided incorrect charset name for type will be thrown internal
error which NPE causes.
Let's provide user-friendly errors for such cases.
Use incorrect charset name:
{code:java}
CREATE TABLE test (c1 CHAR CHARACTER SET UTF_8);{code}
Result:
{code:java}
Caused by: org.apache.ignite.sql.SqlException: IGN-CMN-65535
TraceId:382210fe-335d-4df2-b8fc-149c13b7f5e5 UTF_8
at
java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:732)
at
org.apache.ignite.internal.util.ExceptionUtils$1.copy(ExceptionUtils.java:765)
at
org.apache.ignite.internal.util.ExceptionUtils$ExceptionFactory.createCopy(ExceptionUtils.java:699)
at
org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCause(ExceptionUtils.java:525)
at
org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCauseInternal(ExceptionUtils.java:634)
at
org.apache.ignite.internal.util.ExceptionUtils.copyExceptionWithCause(ExceptionUtils.java:476)
at
org.apache.ignite.internal.sql.api.IgniteSqlImpl.execute(IgniteSqlImpl.java:206)
at
org.apache.ignite.internal.sql.api.PublicApiThreadingIgniteSql.lambda$execute$1(PublicApiThreadingIgniteSql.java:65)
at
org.apache.ignite.internal.thread.PublicApiThreading.executeWithRole(PublicApiThreading.java:144)
at
org.apache.ignite.internal.thread.PublicApiThreading.execUserSyncOperation(PublicApiThreading.java:102)
at
org.apache.ignite.internal.sql.api.PublicApiThreadingIgniteSql.execute(PublicApiThreadingIgniteSql.java:65)
at
org.apache.ignite.internal.sql.sqllogic.ScriptContext.executeQuery(ScriptContext.java:85)
at
org.apache.ignite.internal.sql.sqllogic.Statement.execute(Statement.java:110)
... 5 more
Caused by: java.util.concurrent.CompletionException:
org.apache.ignite.sql.SqlException: IGN-CMN-65535
TraceId:382210fe-335d-4df2-b8fc-149c13b7f5e5 UTF_8
at
org.apache.ignite.internal.sql.api.IgniteSqlImpl.lambda$executeAsyncInternal$5(IgniteSqlImpl.java:379)
at
java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:990)
at
java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:974)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1773)
at
org.apache.ignite.internal.sql.engine.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:83)
... 3 more
Caused by: org.apache.ignite.sql.SqlException: IGN-CMN-65535
TraceId:382210fe-335d-4df2-b8fc-149c13b7f5e5 UTF_8
at
org.apache.ignite.internal.lang.SqlExceptionMapperUtil.mapToPublicSqlException(SqlExceptionMapperUtil.java:61)
... 9 more
Caused by: org.apache.ignite.lang.IgniteException: IGN-CMN-65535
TraceId:382210fe-335d-4df2-b8fc-149c13b7f5e5 UTF_8
at
org.apache.ignite.internal.lang.IgniteExceptionMapperUtil.mapToPublicException(IgniteExceptionMapperUtil.java:118)
at
org.apache.ignite.internal.lang.SqlExceptionMapperUtil.mapToPublicSqlException(SqlExceptionMapperUtil.java:51)
... 9 more
Caused by: java.lang.NullPointerException: UTF_8
at java.base/java.util.Objects.requireNonNull(Objects.java:233)
at
org.apache.calcite.sql.SqlBasicTypeNameSpec.deriveType(SqlBasicTypeNameSpec.java:220)
at
org.apache.calcite.sql.SqlDataTypeSpec.deriveType(SqlDataTypeSpec.java:234)
at
org.apache.ignite.internal.sql.engine.prepare.IgnitePlanner.convert(IgnitePlanner.java:229)
at
org.apache.ignite.internal.sql.engine.prepare.ddl.DdlSqlToCommandConverter.convertCreateTable(DdlSqlToCommandConverter.java:334)
at
org.apache.ignite.internal.sql.engine.prepare.ddl.DdlSqlToCommandConverter.convert(DdlSqlToCommandConverter.java:182)
at
org.apache.ignite.internal.sql.engine.prepare.PrepareServiceImpl.prepareDdl(PrepareServiceImpl.java:245)
at
org.apache.ignite.internal.sql.engine.prepare.PrepareServiceImpl.prepareAsync0(PrepareServiceImpl.java:230)
at
org.apache.ignite.internal.sql.engine.prepare.PrepareServiceImpl.prepareAsync(PrepareServiceImpl.java:210)
at
org.apache.ignite.internal.sql.engine.SqlQueryProcessor.lambda$executeParsedStatement$16(SqlQueryProcessor.java:648)
at
java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1187)
at
java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2309)
at
[jira] [Commented] (IGNITE-21345) TxState and MvccSnapshot removal
[ https://issues.apache.org/jira/browse/IGNITE-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840384#comment-17840384 ] Ilya Shishkov commented on IGNITE-21345: [~av], can you take a look, please? > TxState and MvccSnapshot removal > > > Key: IGNITE-21345 > URL: https://issues.apache.org/jira/browse/IGNITE-21345 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > Time Spent: 10m > Remaining Estimate: 0h > > Remove o.a.i.internal.processors.cache.mvcc.txlog.TxState (as a continuation > of the IGNITE-21130) -- 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] [Commented] (IGNITE-21345) TxState and MvccSnapshot removal
[
https://issues.apache.org/jira/browse/IGNITE-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840383#comment-17840383
]
Ignite TC Bot commented on IGNITE-21345:
{panel:title=Branch: [pull/11323/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11323/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7838424buildTypeId=IgniteTests24Java8_RunAll]
> TxState and MvccSnapshot removal
>
>
> Key: IGNITE-21345
> URL: https://issues.apache.org/jira/browse/IGNITE-21345
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Remove o.a.i.internal.processors.cache.mvcc.txlog.TxState (as a continuation
> of the IGNITE-21130)
--
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] [Created] (IGNITE-22097) JobContext is not closed when job executiong fails
Vadim Pakhnushev created IGNITE-22097: - Summary: JobContext is not closed when job executiong fails Key: IGNITE-22097 URL: https://issues.apache.org/jira/browse/IGNITE-22097 Project: Ignite Issue Type: Bug Components: compute Reporter: Vadim Pakhnushev Assignee: Vadim Pakhnushev When compute job execution fails before the actual execution starts, for example when the task instantiation fails, the job context is not closed leading to the deployment unit not released. -- 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] [Commented] (IGNITE-21938) Cover SQL F041-07(Basic joined table. The inner table in a left or right outer join can also be used in an inner join) feature by tests
[ https://issues.apache.org/jira/browse/IGNITE-21938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840315#comment-17840315 ] Evgeny Stanilovsky commented on IGNITE-21938: - [~jooger] can you make a review plz ? > Cover SQL F041-07(Basic joined table. The inner table in a left or right > outer join can also be used in an inner join) feature by tests > --- > > Key: IGNITE-21938 > URL: https://issues.apache.org/jira/browse/IGNITE-21938 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 3.0.0-beta1 >Reporter: Iurii Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > We don't have at all any tests for F041-07(Basic joined table. The inner > table in a left or right outer join can also be used in an inner join) SQL > feature. > Let's cover it and create tickets to fix them in case find any issues related > to the covered area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-22085) Sql. Support F041-07 feature
[ https://issues.apache.org/jira/browse/IGNITE-22085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky resolved IGNITE-22085. - Resolution: Not A Problem > Sql. Support F041-07 feature > > > Key: IGNITE-22085 > URL: https://issues.apache.org/jira/browse/IGNITE-22085 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 3.0.0-beta1 >Reporter: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > Feature F041-07 (The inner table in a left or right outer join can also be > used in an inner join) is not supported for now. Check current issue mention > in logical tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19670) Improve CatalogService test coverage.
[ https://issues.apache.org/jira/browse/IGNITE-19670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Zhuravkov reassigned IGNITE-19670: - Assignee: Maksim Zhuravkov > Improve CatalogService test coverage. > - > > Key: IGNITE-19670 > URL: https://issues.apache.org/jira/browse/IGNITE-19670 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Maksim Zhuravkov >Priority: Major > Labels: ignite-3, tech-debt-test > > 1. CatalogServiceSelftTest.testCreateTable (+testDropTable) looks a bit > complicated. It checks creation of more than one table. Let's simplify the > test by reverting last changes > 2. We use shared counter to generate unique identifier for schema objects. > Some tests checks schema object id, and some doesn't. Let's move > schema-object's id check into separate test, to verify which command > increments the counter, and which doesn't. > 3. Let's add a test that will check ABA problem. E.g. create-drop-create > table (or index) with same name and check the object can be resolved > correctly by name and by id (regarding object versioning in Catalog, of > course). > 4. Move Catalog operations tests to separate class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
