Hi,
Thanks for replay
I tried to used cache_name, but I still get Exception as below, I have
specify the cache name, I don't know why I still get this error.
I tried to set WRAP_VALUE to false, but it only works for single column.
Did I miss something important?
Caused by: class
Hi,
The only way to change the type of an existing field in a type is to destroy
all caches that contains this type, remove the associated metadata and
recreate the aforementioned caches w/the new type.
You can remove an index.bin file and Ignite will rebuild it w/whatever is in
the associated
Hi,
Please take a look at the documentation of the CREATE TABLE [1]
Use:
CREATE TABLE tableName (id LONG PRIMARY KEY, name VARCHAR)
WITH "|CACHE_NAME=|cacheName"
Please pay attention to other options. Its may be useful to use cache
API & SQL together.
Also be careful when you use cache API
Hi experts,
I'm running ignite server node in k8s and recently I upgraded ignite to
2.10.0. Ignite is started with below command:
/opt/rta/os/jre/bin/java -XX:+AggressiveOpts -Djava.net.preferIPv4Stack=true
-XX:+UseG1GC -XX:+DisableExplicitGC -Dfile.encoding=UTF-8
-DIGNITE_QUIET=false
Hello igniters,
We've recently upgraded from ignite 2.7.6 to 2.10. With the cluster start
we've seen that all indexes are rebuilded which went very well -> no data
loss :)
After upgrade we've run some tests and encountered following problem; we've
following parameter in one of our objects
I tried to query data by partition index, when I insert data using cache API,
I can get data successfully, when I insert data using DML, I can't get data.
*I can get data by partition index using cache API*
IgniteCache cache = ignite.getOrCreateCache("cacheName");
cache.put(1, "v1");
ScanQuery
Hello!
Can you please share complete log from that node?
It seems that the cache for which this Continuous Query was triggered
suddenly went away.
Regards,
--
Ilya Kasnacheev
пт, 7 мая 2021 г. в 01:09, Jigna :
> Hi Team, I got below exception on my ignite server node. Would you please
>