Hello,
we did some benchmarks and did set the copyOnRead flag to false and it did
increase the processing time and the memory a little bit (10%). I cannot
figure out why this would be case since my understanding is that if anything
it should reduce the processing time by avoiding a clone.
One not
Hi,
Just to clarify my words a bit. When persistence is enabled, all memory data
are stored on disk with all durability guarantees. But it is also allows you
to store in cache more data than you can fit in memory: Ignite just evicts
stale data pages from RAM, and when they will be needed - loaded
I am searching one solution to my case. I just found Apache Ignite
Yesterday. It appears a good solution. But I am not sure. I need your
suggestions.
My data is stored in MySQL. It is TB level. I like to do the following:
1. Load all data from MySQL into Ignite.
2. Run sql query to get all data t
Hi
I can not start h2 debug console .
ignite version: 2.1
os: centos6
when I start it by ./ignite.sh , this is the error message:
Hi James,
My answers are inline...
On Sun, Sep 3, 2017 at 3:41 AM, James <2305958...@qq.com> wrote:
> I am searching one solution to my case. I just found Apache Ignite
> Yesterday. It appears a good solution. But I am not sure. I need your
> suggestions.
>
> My data is stored in MySQL. It is T
On Sun, Sep 3, 2017 at 12:35 AM, dkarachentsev
wrote:
> Hi,
>
> Just to clarify my words a bit. When persistence is enabled, all memory
> data
> are stored on disk with all durability guarantees. But it is also allows
> you
> to store in cache more data than you can fit in memory: Ignite just evi
On Sat, Sep 2, 2017 at 5:11 AM, userx wrote:
> Hi all,
>
> Regarding question 2, let me put it this way.
>
> Like ignite has eviction policy for RAM described at
> https://apacheignite.readme.io/docs/evictions
> Is there an eviction policy for a persistent store ? Say for a use case
> where in I
First, I really appreciate a help from Dmitriy.
My company assigns me to work on a big product using Ignite. One node server
is standard and free to all customers. If customers want to use more server,
this product will add modules so the customers can just pay it and use
multiple node computing.
Cross sending to dev@
Igniters, up until version 1.9, the nested fields were supported by
flattening the names. Do we still support it? I cannot seem to find
documentation for it.
D.
On Thu, Aug 31, 2017 at 7:12 AM, takumi wrote:
> This is a part of the real code that I wrote.
>
>
Denis, I think you provided an incorrect link to the ticket. Here is the
correct link:
https://issues.apache.org/jira/browse/IGNITE-3478
D.
On Wed, Aug 30, 2017 at 5:50 PM, Denis Magda wrote:
> Hi,
>
> The docs are still valid - SQL operations are not fully transactional yet
> and, according,
Semyon,
Can you please clarify this. Do we allow concurrent reads while invokeAll
or invoke is executed?
D.
On Tue, Aug 29, 2017 at 11:59 AM, Andrey Kornev
wrote:
> Ah, yes! Thank you, Semyon! According to invokeAll() javadocs "No mappings
> will be returned for EntryProcessors that return a n
James,
I think you will find this documentation useful:
https://apacheignite.readme.io/docs/getting-started
D.
On Sun, Sep 3, 2017 at 8:32 PM, James <2305958...@qq.com> wrote:
> First, I really appreciate a help from Dmitriy.
>
> My company assigns me to work on a big product using Ignite. One
On Mon, Aug 28, 2017 at 5:23 AM, agura wrote:
When persistence store is enabled the data pages that can't be stored in
> the memory will be evicted to the persistence store.
Andrey, this is not how Ignite persistence works.
When the persistence is enabled, all the data will be persisted, witho
13 matches
Mail list logo
