Hello Stephen, the document(ReadMe) you shared earlier, has mentioned that
ignite-calcite must be declared as a dependency.
In this case, it would be, org.apache.ignite:ignite-calcite:2.13.0 right!.
But, which, at the moment, is not available.
Can you please advise?
On Thu, Apr 28, 2022 at 5:21
Note that this is not happening with all the data set but only for cache
entries which were written into ignite before server restart and tried to
be deleted after restart.
On Thu, Apr 28, 2022 at 10:18 PM Sumit Deshinge
wrote:
> Hi,
>
> I am using ignite with native persistence enabled along
Hi,
I am using ignite with native persistence enabled along with cache write
sync mode as FULL_SYNC and cache rebalance mode as sync.
In normal workflow where there is no restart, I can see all data is being
written, read and deleted from cache successfully.
But in case of ignite server
The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.13.0.
Apache Ignite® is a Distributed Database For High-Performance
Computing With In-Memory Speed.
https://ignite.apache.org
The Apache Ignite community has made a lot of changes in the 2.13.0
release. This blog
Seems it would be published with new documentation, Nikita Amelchev isn`t it ?
check [1]
[1] https://issues.apache.org/jira/browse/IGNITE-15189
>Thank you Stephen.
>Is there also a writeup summarizing what is/isn't supported with this
>'experimental' feature?
>On Thu, Apr 28, 2022 at
Hi Team,
We want to use apache ignite for below use case.
We provide reports to customer . We execute query on oracle and feed it into
oracle. And on the top of report, we allow pagination, sorting, grouping and
export etc. Right now for each and every action after report
Thank you Stephen.
Is there also a writeup summarizing what is/isn't supported with this
'experimental' feature?
On Thu, Apr 28, 2022 at 4:30 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> https://github.com/apache/ignite/blob/2.13.0/modules/calcite/README.txt
>
> On 28 Apr
https://github.com/apache/ignite/blob/2.13.0/modules/calcite/README.txt
> On 28 Apr 2022, at 11:46, Lokesh Bandaru wrote:
>
> Thanks Ilya.
>
> Version 2.13 has come out but still seems to be shipping with the same
> vulnerability-ridden version of h2 database.
> The documentation doesn't
Thanks Ilya.
Version 2.13 has come out but still seems to be shipping with the same
vulnerability-ridden version of h2 database.
The documentation doesn't mention if/how Calcite is turned on.
Can you advise on how it can be enabled?
On Wed, Apr 13, 2022 at 7:29 AM Ilya Korol wrote:
> Hi
Got it, can you show both sql requests (with strict and non strict criteria)
and EXPLAIN output in both cases ?
Do you have indexes?
>Hey, it's enabled already. Please check the console log in my email
>On Thu, 28 Apr 2022, 13:16 Zhenya Stanilovsky, < arzamas...@mail.ru > wrote:
>>
>>Hi,
Hey, it's enabled already. Please check the console log in my email
On Thu, 28 Apr 2022, 13:16 Zhenya Stanilovsky, wrote:
>
> Hi, can you check the same with lazy [1] flag ?
>
> [1]
>
Hi, can you check the same with lazy [1] flag ?
[1]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/SqlFieldsQuery.html#setLazy-boolean-
>Hi,
>We are running a sql field query to fetch 4million records from ignite cache.
>We have created a group index for
Hi,
We are running a sql field query to fetch 4million records from ignite
cache. We have created a group index for all fields used in where clause
and can see group index used. But the query takes 20 minutes to fetch all
records. If we provide more strict criteria to fetch only say 500 records,
13 matches
Mail list logo
