Indeed, it would be a very nice interface to have (if anyone has some
free time....)!
I know a few Caltech people who'd like to see how how their WAN
transfer product (http://monalisa.cern.ch/FDT/) would work with HDFS;
if there was a HDFS NIO interface, playing around with HDFS and FDT
would be fairly trivial.
Brian
On Apr 3, 2009, at 5:16 AM, Steve Loughran wrote:
Snehal Nagmote wrote:
can you please explain exactly adding NIO bridge means what and how
it can be
done , what could be advantages in this case ?
NIO: java non-blocking IO. It's a standard API to talk to different
filesystems; support has been discussed in jira. If the DFS APIs
were accessible under an NIO front end, then applications written
for the NIO APIs would work with the supported filesystems, with no
need to code specifically for hadoop's not-yet-stable APIs
Steve Loughran wrote:
Edward Capriolo wrote:
It is a little more natural to connect to HDFS from apache tomcat.
This will allow you to skip the FUSE mounts and just use the HDFS-
API.
I have modified this code to run inside tomcat.
http://wiki.apache.org/hadoop/HadoopDfsReadWriteExample
I will not testify to how well this setup will perform under
internet
traffic, but it does work.
If someone adds an NIO bridge to hadoop filesystems then it would
be easier; leaving you only with the performance issues.
