[
https://issues.apache.org/jira/browse/HADOOP-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HADOOP-4492.
---
Resolution: Duplicate
Being implemented as MAPREDUCE-181.
> Job-specific data on HDFS (job.
+1. Good plan.
--Konstantin
Jitendra Nath Pandey wrote:
Hi,
The changes to configuration keys in HDFS for 21 release are
scheduled to be checked in along with the append changes.
This change was delayed because configuration changes are too many and
merging append code on top of them woul
Add interface classification stable & scope to common
-
Key: HADOOP-6289
URL: https://issues.apache.org/jira/browse/HADOOP-6289
Project: Hadoop Common
Issue Type: Improvement
Affects Ve
On Sep 25, 2009, at 5:31 PM, Jitendra Nath Pandey wrote:
Hi,
The changes to configuration keys in HDFS for 21 release are
scheduled to be checked in along with the append changes.
This change was delayed because configuration changes are too many and
merging append code on top of them woul
+1
On 9/25/09 5:31 PM, "Jitendra Nath Pandey" wrote:
Hi,
The changes to configuration keys in HDFS for 21 release are
scheduled to be checked in along with the append changes.
This change was delayed because configuration changes are too many and
merging append code on top of them would be
I think we should not require Job Q compatibility for 1.0 release.
thanks,
dhruba
On Mon, Sep 28, 2009 at 11:06 AM, Sanjay Radia wrote:
>
> On Sep 28, 2009, at 3:15 AM, Steve Loughran wrote:
>
> Dhruba Borthakur wrote:
>> > It is really nice to have wire-compatibility between clients and serv
On Sep 28, 2009, at 3:15 AM, Steve Loughran wrote:
Dhruba Borthakur wrote:
> It is really nice to have wire-compatibility between clients and
servers
> running different versions of hadoop. The reason we would like
this is
> because we can allow the same client (Hive, etc) submit jobs to t
+1.
On Sep 25, 2009, at 10:16 AM, Owen O'Malley wrote:
We are getting closer to being able to release a Common/HDFS/
MapReduce 1.0. I'd hope that we'll get the last set of things in to
0.22 that mean that it would be labelled 1.0. Toward that end, I'd
like to start locking down the APIs th
+1
On Sep 25, 2009, at 10:16 AM, Owen O'Malley wrote:
We are getting closer to being able to release a Common/HDFS/MapReduce
1.0. I'd hope that we'll get the last set of things in to 0.22 that
mean that it would be labelled 1.0. Toward that end, I'd like to start
locking down the APIs that we'
HBase and similar HDFS clients could benefit from a (high) performant
stable datacenter network protocol that is built into the namenode and
datanodes. Then we could decouple from Hadoop versioning and release
cycle. HDFS could decouple from core, etc.
Whatever stable network protocol is devised
Dhruba Borthakur wrote:
It is really nice to have wire-compatibility between clients and servers
running different versions of hadoop. The reason we would like this is
because we can allow the same client (Hive, etc) submit jobs to two
different clusters running different versions of hadoop. But
11 matches
Mail list logo
