[ 
https://issues.apache.org/jira/browse/IGNITE-14845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477210#comment-17477210
 ] 

Andrey Mashenkov edited comment on IGNITE-14845 at 1/17/22, 1:32 PM:
---------------------------------------------------------------------

[~eliasbalasis] ,
Unfortunately,
 # it is impossible to upgrade H2 due to broken compatibility with Ignite on H2 
side in late versions.
 # including H2 code is impossible as well due to legal reasons.

Seems, the only way is to create a new module with H2 4.1.197 code and build 
Ignite manually using the maven shade plugin [1]. 
This will allow you and  Ignite to use different H2 versions. 

An alternative is to be patient and wait for the new SQL engine based on Apache 
Calcite.

 [1]https://maven.apache.org/plugins/maven-shade-plugin/


was (Author: amashenkov):
[~eliasbalasis] ,
Unfortunately,
 # it is impossible to upgrade H2 due to broken compatibility with Ignite on H2 
side in late versions.
 # including H2 code is impossible as well due to legal reasons.

Seems, the only way is to create a new module with H2 4.1.197 code and build 
Ignite manually using the maven shade plugin [1]. 
This will allow you and  Ignite to use different H2 versions. 

 [1]https://maven.apache.org/plugins/maven-shade-plugin/

> Upgrade H2 or enclose in Ignite classpath
> -----------------------------------------
>
>                 Key: IGNITE-14845
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14845
>             Project: Ignite
>          Issue Type: Improvement
>          Components: h2-limitation
>    Affects Versions: 2.10
>            Reporter: Elias Balasis
>            Priority: Major
>
> When using Apache Ignite with SpringBoot or other dependency chains we are 
> forced to downgrade H2 to 4.1.197 which breaks other relationships besides 
> making the classpath fragile and less maintainable besides causing runtime 
> conflicts.
> It would be very welcome if H2 could be upgraded to 4.1.200
> Ideally, H2 should be enclosed in Apache Ignite classpath which is the way 
> GridGain Ignite handles this problem, without a direct dependency on H2 
> itself but enclosing H2 instead in internal packages.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to