[ http://issues.apache.org/jira/browse/HADOOP-337?page=comments#action_12418809 ]
eric baldeschwieler commented on HADOOP-337: -------------------------------------------- We generally support Paul's prioritization. But we are also going to be moving up the tempo and volume of data we manage in the system, "A LOT". If we find a small list of features to be cost effective investments, we'd like to be able to give them back to the community. If it makes sense for us to invest significant man-power to produce a patch for this and can validate that said patch does not destabilize large clusters over a significant period of operation, I'd assume this wouldn't be that controversial, since this is a very natural extension of the API that does seem eventually inevitable (along with multiple appenders, which would be very, very helpful). I think the thing we need to agree on is the testing criteria for acceptance, so we're not constantly derailing the community. Do folks agree with the above? If so, let's put more energy into thinking about how we are going to establish a testing / validation regime that will support innovation, rather than trying to kill innovation for safety's sake. That way lies madness. We'll be happy to help staff / fund such a testing policy. (Anyone want to create an "enhancement" to discuss HDFS extension validation?) > DFS files should be appendable > ------------------------------ > > Key: HADOOP-337 > URL: http://issues.apache.org/jira/browse/HADOOP-337 > Project: Hadoop > Type: New Feature > Components: dfs > Versions: 0.1.0, 0.2.0, 0.1.1, 0.3.0, 0.4.0, 0.2.1, 0.3.1, 0.3.2 > Environment: all > Reporter: Runping Qi > > Actually two related issues > 1. One should be able to open an existing DFS file, to seek to a position and > truncate the rest, and to append starting at the end (or where trancation > happens) . > 2. One should be able to read the writen data of a DFS file while other is > writing/appending to the file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
