[
https://issues.apache.org/jira/browse/HDFS-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE resolved HDFS-4464.
--
Resolution: Fixed
Fix Version/s: Snapshot (HDFS-2802)
Hadoop Flags: R
Suresh Srinivas created HDFS-4465:
-
Summary: Optimize datanode ReplicasMap and ReplicaInfo
Key: HDFS-4465
URL: https://issues.apache.org/jira/browse/HDFS-4465
Project: Hadoop HDFS
Issue Type:
Tsz Wo (Nicholas), SZE created HDFS-4464:
Summary: Combine collectSubtreeBlocksAndClear with
deleteDiffsForSnapshot
Key: HDFS-4464
URL: https://issues.apache.org/jira/browse/HDFS-4464
Project:
On Thu, Jan 31, 2013 at 12:12 PM, Arun C Murthy wrote:
> I apologize if there was too much technical details.
>
> The simplified version is that hadoop-2 isn't baked as it stands today,
> and is not viable to be supported by this community in a stable manner. In
> particular, it is due to the mov
On Fri, Feb 1, 2013 at 2:34 AM, Tom White wrote:
> Possibly the reason for Stack's consternation is that this is a
> Hadoop-specific versioning scheme, rather than a standard one like
> Semantic Versioning (http://semver.org/) which is more widely
> understood.
If I can offer an alternate and l
On Wed, Jan 30, 2013 at 11:32 PM, Vinod Kumar Vavilapalli
wrote:
> I still have a list of pending API/protocol cleanup in YARN that need to be
> in before we even attempt supporting compatibility further down the road.
To let others track these it would be useful if they were tagged in
JIRA with
Possibly the reason for Stack's consternation is that this is a
Hadoop-specific versioning scheme, rather than a standard one like
Semantic Versioning (http://semver.org/) which is more widely
understood.
With that scheme we would have something like
2.0.0-alpha, 2.0.0-alpha.1, 2.0.0-alpha.2, 2
