No, IGFS will not work without that URL. I'm not sure how com.mapr.fs.MapRFileSystem exactly works, but I suppose that you can specify any MapR Fs node host there. One of possible ideas is to specify "localhost" as the 2ndary Fs URI, assuming each host running Ignite node is a MapR Fs node. Though, such configuration should be checked for correct work in practice.
On Wed, May 17, 2017 at 7:03 PM, Pranay Tonpay <[email protected]> wrote: > 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" <[email protected]> > wrote: > >> Hi, Pranay, >> IGFS can run upon any file system that can be represented in terms of >> Hadoop >> file system API (namely as a org.apache.hadoop.fs.FileSystem). >> MapR file system also implements Hadoop file system API , namely, it has >> com.mapr.fs.MapRFileSystem . >> So, IGFS can successfully run upon. >> Though, it may also be true that in such mode Ignite will not be able to >> utilize all MapR Fs advantages, because Ignite does not have native >> integration with MapR Fs . >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Igfs-and-MaprFs-tp12897p12977.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> >
