[
https://issues.apache.org/jira/browse/IGNITE-14845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476274#comment-17476274
]
Elias Balasis edited comment on IGNITE-14845 at 1/14/22, 4:58 PM:
------------------------------------------------------------------
The main reason for downgrading is, like I said, requirement by Apache ignite.
It doesn't work with anything different to what it was built with.
Therefore I have to have in the classpath the version of H2 that the version of
Apache Ihnite I am using was built with, in this case 4.1.197, which can have
unredictable classpath related runtime side effects besides making the
classpath fragile.
was (Author: eliasbalasis):
The main reason for downgrading is, like I said, requirement by Apache ignite.
It doesn't work with anything different to what it was built with.
Therefore I have to have in the classpath the version of H2 that the version of
Apache Ihnite I am using was built with, in this case 4.1.197, which can have
unredictable classpath related runtime side effects besides making the lasspath
fragile.
> 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)
