ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Mashenkov (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10801) Upgrade H2 version up to 1.4.199
Date Thu, 28 Nov 2019 11:28:00 GMT

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

Andrey Mashenkov commented on IGNITE-10801:

I've failed while trying to upgrade H2 up to 1.4.199.
There are 2 issues that should be resolved at first as we can't rollback 2-3 commits from
H2 code as it is already released.

The first one is names (e.g function) quotation policy are changed and this cause too many
Ignite test failures.
The second one is multi-statement queries will run in parallel from 1.4.199, and this cause
major changes in Ignite.

Also, ticket description is unclear. 
Now, regarding IEP-37 [1], this doesn't look worth an effort.
What exact fixes are important for Ignite that makes ticket priority critical?

[1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine

> Upgrade H2 version up to 1.4.199
> --------------------------------
>                 Key: IGNITE-10801
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10801
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 2.7
>            Reporter: Sergey Antonov
>            Priority: Critical
>              Labels: sql
>             Fix For: 2.8
>          Time Spent: 20m
>  Remaining Estimate: 0h
> After h2 1.4.199 release we should upgrade h2 version using in AI, because of important
bugs will be fixed there. For example https://github.com/h2database/h2database/issues/1057

This message was sent by Atlassian Jira

View raw message