Greetings,<br><br>I am not sure I understand fully the relationship b/w glusterfs project per se and <a href="https://github.com/gluster/hadoop-glusterfs">https://github.com/gluster/hadoop-glusterfs</a>, but I'd like to follow up on the "Hadoop Connector" mention here (<a href="http://www.gluster.org/community/documentation/index.php/Hadoop">http://www.gluster.org/community/documentation/index.php/Hadoop</a>) and getFileBlockLocations API mention here (<a href="http://community.gluster.org/q/how-gluster-supports-map-reduce-in-absence-of-metadata-of-input-data-chunks-spread-over-multiple-machines-see-desciption/">http://community.gluster.org/q/how-gluster-supports-map-reduce-in-absence-of-metadata-of-input-data-chunks-spread-over-multiple-machines-see-desciption/</a>):<br>
<br>- does 3.3 install any kind of a C lib that would allow for "where data actually landed" queries?<br><br>This would be very useful to users who want to structure their HPC jobs in the map/reduce style, but without using Hadoop specifically. (Really, the main innovation in MapReduce is colocation of calculation and data and I'd rather use a fs that's mountable in the classic sense as opposed to HDFS).<br>
<br>Regards,<br>Vlad <br>