Hi Vladimir! I will be absolutely happy to help.
Let's discuss in telegram.
ср, 24 июн. 2020 г. в 02:31, Denis Magda :
> Hello Vladimir,
>
> Sounds interesting, thanks for reaching out. Let me introduce you to @Kseniya
> Romanova who can help with the publication
> process.
>
> -
> Denis
>
>
>
Hello Vladimir,
Sounds interesting, thanks for reaching out. Let me introduce you to @Kseniya
Romanova who can help with the publication process.
-
Denis
On Sun, Jun 21, 2020 at 10:31 PM Vladimir Tchernyi
wrote:
> Hi Denis,
>
> Some progress had happened and I have some material to share
Hello!
I think in your QueryEntity you need to declare an index of type
QueryIndexType.FULLTEXT.
Regards,
--
Ilya Kasnacheev
вт, 23 июн. 2020 г. в 19:35, ram.gaurav.chhabra <
ram.gaurav.chha...@gmail.com>:
> Hello All,
>
> Currently working on one module which is using Apache Ignite and all
Hello All,
Currently working on one module which is using Apache Ignite and all
configuration is driven through XML(ignite-default.xml).
Got one requirement where-in i need to implement full text search which can
be achieved by *@QueryTextField*
I have done this change and annotated respective
Hi,
I am evaluating Apache Ignite for a use case where I know we may not have
enough RAM to store the entire database. For example we might store 30 days
of data, but only have enough memory for 15, and in fact most of the queries
will be against the last 5 days of data. I am doing some tests
Hi,
Starvation messages contain queue information, showing which tasks are
pending.
Looks like you are overloading the system w/too many requests/queries
that are taking a long time.
Send over log/reproducer/config/version #s/heap sizes and I'll take a
look. Take a thread dump using
We are getting these warnings quite often
```
./ignite-3fb86334.0.log:[09:48:02,663][WARNING][grid-timeout-worker-#71][IgniteKernal]
Possible thread pool starvation detected (no task completed in last 3ms,
is query thread pool size large enough?)
