Caches can store objects of any type, there are no restrictions for "a
value type per caches". SQL tables support the following data types:
https://apacheignite-sql.readme.io/docs/data-types
-
Denis
On Mon, Apr 29, 2019 at 11:52 PM Scott Cote wrote:
> What are the restrictions around having tw
Hi,
Are you thinking of deploying Ignite as a shared layer on top of the
sources? If that's the case then attach those sources to your in-memory
cluster via the CacheStore interface:
https://apacheignite.readme.io/docs/3rd-party-store
-
Denis
On Mon, Apr 29, 2019 at 9:54 AM Enrique Medina Mont
I currently am running a 10 node Ignite cluster on EKS. I tried running it
was a k8s deployment, but the thrash in getting all the nodes to join and
agree on a topology was pretty painful, so its running currently as a
statefulset.
Currently, the issue I am seeing is that when I try to deploy a cl
At this point I've spent enough time on this problem and can move on with my
project without using @QueryTextField--I'm just letting anyone who's
concerned know what I've seen in case you want to probe into this issue any
further.
I've taken the time to write a reproducer that can be easily run o
Hi All
If I choose binary data type for my objects, as opposed to varchar, will it
result in any saving, and yes, how much?
I know that binary type would be faster to read/write but wanted to see if
there will be any saving in storage.
thanks
Clay
Hello!
My guess is that you have non-matching -Djava.net.preferIPv4Stack=true in
your cluster (some nodes have it, some don't).
It is recommended to use this setting on all nodes, including Visor.
There is a ticket about similar behavior:
https://issues.apache.org/jira/browse/IGNITE-8343
Regard
Hi,
Lucene indexes are stored in the heap, while I see that in reproducer
you've limited heap size to 1gb. Are you sure that you used these JVM opts?
Can you please share logs from your run, so I can check the heap usage?
Best Regards,
Evgenii
вт, 30 апр. 2019 г. в 00:23, kellan :
> The issue s
