Hi,
Can someone please point me to a good example of Camel routes with -
1) ignite topic as receiving end point
2) ignite cache as receiving end point
3) ignite event as receiving end point
I know that this question could be for Apache Camel community too, but if
someone can give any pointer here,
y,
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, Pran
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
Hi,
I have setup igfs as a caching layer on top of a HA configured hadoop
cluster.. few questions ~
1) if I put data on hdfs directly, and then read it via ignite, the data
would get cached in ignite and any subsequent fetches wud fetch it from
igfs and not go to hdfs at all... Correct?
2) if after
Thx Ivan ...
Thr is a parameter for uri for class ignitehadoopigfssecondaryfilesystem in
the config which is for specifying namenode host and port .. in case of
MapR shud we leave it empty then?
On May 17, 2017 8:32 AM, "Ivan Veselovsky"
wrote:
> Hi, Pranay,
> IGFS can run upon any file system t
Hi,
On the ignite site, it does have links that talk about running igfs on top
of Apache hadoop, hdp and cdh but there is no mention of MapR ... Is it due
to the no namenode architecture of MapR that it is not supported?
Pls advise
Thx Ivan, that helps
On May 16, 2017 10:24 AM, "Ivan Veselovsky"
wrote:
Hi, Pranay,
> Does it mean that Namenode can be avoided when IGFS get deployed on top of
> HDFS ?
No. IGFS itself does not have namenode, it is a distributed cache storing
file blocks. But when deployed on top of HDFS, it f
hi ,
I am new to Ignite and have been exploring the usage of ignite as a caching
layer with HDFS filesystem underneath -
There was a mention that there was no need of a namenode using IGFS as it
can determine the file data locality using the hashing function.
Does it mean that Namenode can be avoid
