Hi Ivan,
Sorry , I am using my phone to type as emails are blocked in the
organization..
Example ~
IgniteCache cache = ignite.getorcreatecache("my cache")
Cache.put(key, value) ...
For the above, I am assuming there is no write thru cache implementation to
write to Hdfs ... One wud have to implement the cachestore interface and
have the logic written... There r implementations for rdbms but not for
Hdfs.. I understand the reason why it may not be there due to immutability
of Hdfs, but wanted to confirm on this...
On May 19, 2017 10:16 AM, "Ivan V." <iveselovs...@gridgain.com> wrote:
Hi, Pranay,
to be honest, I'm not sure I 100% understand the question.
Yes, IGFS internally implemented by 2 caches (meta & data), but these 2
caches do not assume any direct modifications, that is, modifications done
otherwise than through IGFS API.
On Fri, May 19, 2017 at 7:12 PM, Pranay Tonpay <pton...@gmail.com> wrote:
> Thx Ivan.. appreciate your help...
>
> Regarding point 3, I was specifically referring to the IgniteCache and not
> Igfs. Sorry if my jargons are a bit incorrect in the context, but per my
> understanding, ignite has ~
> 1) in memory data grid (ignite cache)
> 2) ignite file system
>
> 2 sits on top of 1 (rather makes use of 1) ...
> Doing anything on igfs (2) does reflect in hdfs as expected, but
> manipulating cache (key value pairs), which is (1) ,simply remain in
> memory, unless I implement the CacheStore interface for hdfs and implement
> load, write etc ..
> Is that correct interpretation?
>
> Pls opine...
>
>
> On May 19, 2017 5:20 AM, "Ivan Veselovsky" <iveselovs...@gridgain.com>
> wrote:
>
> 1) Yes, unless some data have been evicted from Ignite cache.
> 2) Sure, this is expected: IGFS in dual modes always tries to reflect the
> underlying file system contents.
> 3) This sounds strange. In DUAL_ASYNC mode it is possible that changes made
> to IGFS appear in underlying file system with some delays, but they should
> appear eventually. In DUAL_SYNC mode the changes should appear immediately
> upon operation completion.
>
>
>
> --
> View this message in context: http://apache-ignite-users.705
> 18.x6.nabble.com/Few-questions-tp13004p13027.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>
>
