You are fast. :) Was just typing a reply on top of the last one and yours
is already here.

Ignore the last question, found this,
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13 .
*Looking forward to this release. *

*One slightly unrelated question, feel free to ignore. *
*I know there is no support(or certified) for any version of Java greater
than 11. *
*What would it take for 2.13 to be able to run on Java17?*

On Tue, Apr 12, 2022 at 3:36 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:

> Code freeze was yesterday. The target release date is 22 April.
>
> More here: Apache+Ignite+2.13
> <https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13>
>
> On 12 Apr 2022, at 11:03, Lokesh Bandaru <lokeshband...@gmail.com> wrote:
>
> Thanks for getting back, Stephen.
> I am aware that Calcite is in the plans.
> Any tentative timeline as to when 2.13(beta/ga) is going to be made
> available?
>
> Regards.
>
> On Tue, Apr 12, 2022 at 2:15 PM Stephen Darlington <
> stephen.darling...@gridgain.com> wrote:
>
>> The H2 project removed support for Ignite some time ago (
>> https://github.com/h2database/h2database/pull/2227) which makes it
>> difficult to move to newer versions.
>>
>> The next version of Ignite (2.13) has an alternative SQL engine (Apache
>> Calcite) so over time there will be no need for H2.
>>
>> On 11 Apr 2022, at 20:34, Lokesh Bandaru <lokeshband...@gmail.com> wrote:
>>
>> Resending.
>>
>> On Mon, Apr 11, 2022 at 6:42 PM Lokesh Bandaru <lokeshband...@gmail.com>
>> wrote:
>>
>>> Hello there, hi
>>>
>>> Writing to you with regards to the security vulnerabilities(particularly
>>> the most recent ones, CVE-2022-xxx and CVE-2021-xxx) in the H2 database and
>>> the Apache Ignite's dependency on the flagged versions of H2.
>>> There is an open issue tracking this,
>>> https://issues.apache.org/jira/browse/IGNITE-16542, which doesn't seem
>>> to have been fully addressed yet.
>>> Have these problems been overcome already? Can you please advise?
>>>
>>> Thanks.
>>>
>>
>>
>

Reply via email to