Hello!
Nothing obvious is wrong here. Can you please enable DEBUG logging for
org.apache.ignite.cache.store.jdbc
re-run your case and share the logs?
Regards,
--
Ilya Kasnacheev
пн, 21 янв. 2019 г. в 18:04, shivakumar :
> Hi here is my cache store configuration
>
>
>
>
> http://www.springf
Hi here is my cache store configuration
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:util="http://www.springframework.org/schema/util";
xsi:schemaLocation="http://www.springframework.org/schema/beans
Hello!
What Cache Store implementation are you using, and which are its settings?
Regards,
--
Ilya Kasnacheev
ср, 16 янв. 2019 г. в 21:43, shivakumar :
> Hi
> i am trying to use hive as 3rd party persistence store and enabled write
> behind and i set these cache configurations using spring xm
Hi
i am trying to use hive as 3rd party persistence store and enabled write
behind and i set these cache configurations using spring xml
every 5000ms interval ignite updating only one recored
Thanks Ivan for confirming my suspicions around the query support for Hive.
I did attempt the SQLServerDialect as well but had the same results.
I did get a success message for the load but no data was actually loaded
into the cache so it appears that was a false positive.
--
Sent from: http:/
FileSystem
> implementation of IGFS. The intent of using 3rd party persistence with
> Hive
> instead of IGFS is to avoid tightly coupling Ignite with our Hadoop
> environment.
>
> It appears to me that the SQL being generated by Ignite to communicate with
> Hive via the driver i
3rd party
persistence?
Just to be clear, I am not trying to implement the IgniteHadoopFileSystem
implementation of IGFS. The intent of using 3rd party persistence with Hive
instead of IGFS is to avoid tightly coupling Ignite with our Hadoop
environment.
It appears to me that the SQL being generated
