Vij,
Yes, cache store is normally used when you want to cache as much data from
it as possible. In your case you have two separate data processing modes -
one for hot data with possible caching, and another one for historical
data.
It seems to me that you could just put Ignite cache "near"
Hi Vladimir,Not really, we do not want to store historical data in cache or may
be cache it for few hours and then evict it.But if recent data is missing in
cache then yes we want to cache it.So it would require some custom caching
logic to decide which data to cache.So seems like storing
Could you tell more about it ? How to do it ?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Data-Grid-with-write-through-mode-to-HDFS-with-layer-of-IGFS-tp4122p4171.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Vij,
Storing hot recent data in cache, and historical data in persistent store
sounds like a perfectly reasonable idea.
If you decide to store historical data in HDFS, then you should be able to
construct HDFS path from the key because store interface accepts keys to
store/load data. If this
Thanks Vladimir !!
The drawback with using HDFS as persistent store behind Ignite cache is how we
will take care of appending single key value pair to HDFS file.Ideally we
should use some NoSQL store or RDBMS as persistent back up behind Ignite cache
and then run some scheduled batch to
Vij,
No, it doesn't. IGFS serves the very different purpose - it is
Hadoop-compatible file system. It means that, for example, you can load
data to IGFS and then query it using Hive. But native Ignite SQL is not
applicable here.
Vladimir.
On Wed, Apr 13, 2016 at 3:55 PM, vijayendra bhati
Thanks Vladimir,
I have not gone through complete documentation but if you could let me know
does IGFS provide SQL support like Ignite cache does ?
Regards,Vij
On Wednesday, April 13, 2016 5:54 PM, Vladimir Ozerov
wrote:
Hi Vijayendra,
IGFS is designed to be a