Configuration sends too much data to log4j
--
Key: HADOOP-6312
URL: https://issues.apache.org/jira/browse/HADOOP-6312
Project: Hadoop Common
Issue Type: Improvement
Components: conf
There is a python interface to access HDFS files if that helps your case :
http://wiki.apache.org/hadoop/HDFS-APIs
thanks,
dhruba
On Tue, Oct 13, 2009 at 12:00 PM, Huy Phan wrote:
> Hi Brian,
> Thank you for posting your solution here, I will try this on my testing
> server and do some load tes
Hi Brian,
Thank you for posting your solution here, I will try this on my testing
server and do some load tests.
Also thank you for pointing out some leaks inside libhdfs. Actually I'm
writing a Python extension for HDFS and noticed some Memory Leaks, but I
was not sure if it's the bug of my ex
Hello,
I am new to hadoop. I have 4 databases with different files in each one of
them. Say, images in one, video, documents etc. My task is to develop a web
service which accepts the keyword from the client and it should come to HDFS
and the output/ the file has to go back to the client.
I have
Hey Huy,
Heres what we do:
1) include hdfsJniHelper.h
2) Do the following when you're done with the filesystem:
if (NULL != fs) {
//Get the JNIEnv* corresponding to current thread
JNIEnv* env = getJNIEnv();
if (env == NULL) {
ret = -EIO;
} else {
//
Hi Eli,
You're right that the problem is resolved in 0.20 with function
newInstance(), unfortunately my system's running on Hadoop 0.18.3 and
i'm still looking for a way to patch this version without affecting the
current system.
Regards,
Huy Phan
Eli Collins wrote:
Hey Huy,
What versio
Hey Huy,
What version of hadoop are you using? I think HADOOP-4655 may have
resolved the issue you're seeing but I think is only in 20 and later.
Thanks,
Eli
On Mon, Oct 12, 2009 at 8:52 PM, Huy Phan wrote:
> Hi All,
> I'm writing a multi-thread application using libhdfs in C, a known issue
Hi All,
I'm writing a multi-thread application using libhdfs in C, a known issue
of HDFS is that the FileSystem API caches FileSystem handles and always
returned the same FileSystem handle when called from different threads. It
means even though I called hdfsConnect for many times, I should not