FAQ
[ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719212#action_12719212 ]

Todd Lipcon commented on HADOOP-2366:
-------------------------------------

Patch looks OK, but why not use str.split("\\s*,\\s*") as suggested by Craig above? Then you can simply use Arrays.asList and not have to iterate over the split array to create an ArrayList.
Space in the value for dfs.data.dir can cause great problems
------------------------------------------------------------

Key: HADOOP-2366
URL: https://issues.apache.org/jira/browse/HADOOP-2366
Project: Hadoop Core
Issue Type: Bug
Components: conf
Reporter: Ted Dunning
Assignee: Todd Lipcon
Attachments: HADOOP-2366.patch


The following configuration causes problems:
<property>
<name>dfs.data.dir</name>
<value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
<description>
Determines where on the local filesystem an DFS data node should store its bl
ocks. If this is a comma-delimited list of directories, then data will be stor
ed in all named directories, typically on different devices. Directories that
do not exist are ignored.
</description>
</property>
The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

  • Todd Lipcon (JIRA) at Jun 15, 2009 at 5:20 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719655#action_12719655 ]

    Todd Lipcon commented on HADOOP-2366:
    -------------------------------------

    I think this patch changes the behavior of getStrings when the configured value is the empty string "":

    {noformat}
    bsh % System.out.println("".split("\\s*,\\s*").length);
    1
    bsh % System.out.println("".split("\\s*,\\s*")[0]);

    bsh % import java.util.StringTokenizer;
    bsh % StringTokenizer tk = new StringTokenizer("", ",");
    bsh % System.out.println(tk.hasMoreTokens());
    false
    {noformat}

    maybe the condition just needs the additional !str.trim().equals("")
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Core
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Todd Lipcon
    Attachments: HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hadoop QA (JIRA) at Jun 15, 2009 at 10:46 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719832#action_12719832 ]

    Hadoop QA commented on HADOOP-2366:
    -----------------------------------

    -1 overall. Here are the results of testing the latest attachment
    http://issues.apache.org/jira/secure/attachment/12410578/HADOOP-2366.patch
    against trunk revision 784663.

    +1 @author. The patch does not contain any @author tags.

    +1 tests included. The patch appears to include 3 new or modified tests.

    +1 javadoc. The javadoc tool did not generate any warning messages.

    +1 javac. The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs. The patch does not introduce any new Findbugs warnings.

    +1 Eclipse classpath. The patch retains Eclipse classpath integrity.

    +1 release audit. The applied patch does not increase the total number of release audit warnings.

    -1 core tests. The patch failed core unit tests.

    -1 contrib tests. The patch failed contrib unit tests.

    Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/499/testReport/
    Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/499/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
    Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/499/artifact/trunk/build/test/checkstyle-errors.html
    Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/499/console

    This message is automatically generated.
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Core
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Todd Lipcon
    Attachments: HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Todd Lipcon (JIRA) at Jun 16, 2009 at 12:12 am
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719866#action_12719866 ]

    Todd Lipcon commented on HADOOP-2366:
    -------------------------------------

    Lots of test failures on this one. Michele: can you look into these failures please? Thanks
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Core
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Todd Lipcon
    Attachments: HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Todd Lipcon (JIRA) at Jun 16, 2009 at 5:21 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720243#action_12720243 ]

    Todd Lipcon commented on HADOOP-2366:
    -------------------------------------

    Tsz Wo: In reviewing this patch, I grepped for other usages of StringUtils.getStrings and getStringCollection. It appears to me that the only user other than Configuration is StreamJob for handling some command line flags (where the whitespace trimming also makes good sense). Inside Configuration, it's used for getClasses as well as various file-path related things. Looking at uses of conf.getStrings I also can't find any that look like they would cause an issue.

    If tests pass after fixing the behavior on an empty conf, do you have an issue with changing the semantics of these utility functions so long as the new behavior is clearly documented in the javadoc?
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Core
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Todd Lipcon
    Attachments: HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Tsz Wo (Nicholas), SZE (JIRA) at Jun 16, 2009 at 8:35 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720335#action_12720335 ]

    Tsz Wo (Nicholas), SZE commented on HADOOP-2366:
    ------------------------------------------------
    If tests pass after fixing the behavior on an empty conf, do you have an issue with changing the semantics of these utility functions so long as the new behavior is clearly documented in the javadoc?
    Configuration is a public class and is not a part of fs or hdfs. Trimming the string values may make sense in fs/hdfs paths but it may not for the other usages. Personally, I wish the trimming was done in the beginning. Unfortunately, it was not. If we change it now, then it breaks existing semantics. I think that users rarely use leading or tailing spaces in configuration values but we cannot break them.

    When I worked on HADOOP-2461, I think that the property names should be trimmed but not the values. Otherwise, it forbids the potential use of leading and trailing spaces. If there is a need, the codes using the conf values should do the trimming. In this issue, only the values for dfs.data.dir should be trimmed.

    If a trimmed version of getStrings(..) is needed, I think it is better to provide new methods, say getTrimmedStrings(..) in Configuration and StringUtils but not changing the existing ones.
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Core
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Todd Lipcon
    Attachments: HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Raghu Angadi (JIRA) at Jun 17, 2009 at 12:48 am
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720444#action_12720444 ]

    Raghu Angadi commented on HADOOP-2366:
    --------------------------------------

    New interface sounds better. NameNode also reads a list of directories. Could you check if this fix is required there as well?
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Core
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Todd Lipcon
    Attachments: HADOOP-2366-trimmed.patch, HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Todd Lipcon (JIRA) at Jun 18, 2009 at 3:38 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721314#action_12721314 ]

    Todd Lipcon commented on HADOOP-2366:
    -------------------------------------

    Can someone with the correct privileges make Michele a contributor and reassign this issue?
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Core
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Todd Lipcon
    Attachments: HADOOP-2366-trimmed.patch, HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Michele (aka pirroh) Catasta (JIRA) at Jun 26, 2009 at 12:11 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724496#action_12724496 ]

    Michele (aka pirroh) Catasta commented on HADOOP-2366:
    ------------------------------------------------------

    Is there something I should do to trigger again the Hudson build with the new patch?
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Common
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Michele (aka pirroh) Catasta
    Attachments: HADOOP-2366-trimmed.patch, HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Tsz Wo (Nicholas), SZE (JIRA) at Jun 26, 2009 at 6:20 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724644#action_12724644 ]

    Tsz Wo (Nicholas), SZE commented on HADOOP-2366:
    ------------------------------------------------

    After the project split, this problem needs two separated patches, one for Common and the other one for HDFS. I think we should change Configuration and StringUtils in this issue and create a new HDFS issue for the rest.
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Common
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Michele (aka pirroh) Catasta
    Attachments: HADOOP-2366-trimmed.patch, HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Tsz Wo (Nicholas), SZE (JIRA) at Jun 30, 2009 at 1:27 am
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725420#action_12725420 ]

    Tsz Wo (Nicholas), SZE commented on HADOOP-2366:
    ------------------------------------------------

    Michele, could you run "ant test-patch" and "ant test" over your patch, and then post the results?
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Common
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Michele (aka pirroh) Catasta
    Attachments: HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Michele (aka pirroh) Catasta (JIRA) at Jun 30, 2009 at 12:21 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725591#action_12725591 ]

    Michele (aka pirroh) Catasta commented on HADOOP-2366:
    ------------------------------------------------------

    Tsz Wo: build successful for "ant test"


    {code}
    -1 overall.
    +1 @author. The patch does not contain any @author tags.
    +1 tests included. The patch appears to include 3 new or modified tests.
    +1 javadoc. The javadoc tool did not generate any warning messages.
    -1 javac. The applied patch generated 64 javac compiler warnings (more than the trunk's current 124 warnings).
    +1 findbugs. The patch does not introduce any new Findbugs warnings.
    +1 release audit. The applied patch does not increase the total number of release audit warnings.
    {code}


    for "ant test-patch". No idea about the warnings, probably I messed up something in forrest/findbugs?
    Space in the value for dfs.data.dir can cause great problems
    ------------------------------------------------------------

    Key: HADOOP-2366
    URL: https://issues.apache.org/jira/browse/HADOOP-2366
    Project: Hadoop Common
    Issue Type: Bug
    Components: conf
    Reporter: Ted Dunning
    Assignee: Michele (aka pirroh) Catasta
    Attachments: HADOOP-2366.patch


    The following configuration causes problems:
    <property>
    <name>dfs.data.dir</name>
    <value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
    <description>
    Determines where on the local filesystem an DFS data node should store its bl
    ocks. If this is a comma-delimited list of directories, then data will be stor
    ed in all named directories, typically on different devices. Directories that
    do not exist are ignored.
    </description>
    </property>
    The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
    My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedJun 14, '09 at 1:08a
activeJun 30, '09 at 12:21p
posts12
users1
websitehadoop.apache.org...
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase