On Wed, Jan 29, 2014 at 12:30 PM, Jason Lowe wrote:
> It is a bit concerning that the JIRA history showed that the target version
> was set at some point in the past but no record of it being cleared.
Perhaps the version itself was renamed?
Doug
On Fri, Oct 11, 2013 at 9:14 AM, Milind Bhandarkar
wrote:
> If HDFS is released independently, with its own RPC and protocol versions,
> features such as pluggable namespaces will not have to wait for the next
> mega-release of the entire stack.
The plan as I understand it is to eventually be a
On Mon, Oct 7, 2013 at 12:05 PM, Andrew Purtell wrote:
> I recognize some of what we recently experienced on a HDFS matter in what
> Milind wrote even if this was not the appropriate forum for it. Odd mention
> of "conspiracy theories" aside, for people who may come to this thread
> later, perhaps
On Sun, Oct 6, 2013 at 5:58 PM, Milind Bhandarkar
wrote:
> Is Hortonworks concerned that this proposal conflicts with their
> development on federated namenode ?
This question might better be asked directly of folks at Hortonworks
rather than here.
Let's please not dwell on such aspects here, ke
On Fri, Aug 9, 2013 at 1:15 PM, Alejandro Abdelnur wrote:
> pinging again, I need help from somebody with sudo access to the hadoop
> jenkins boxes to do this or to get sudo access for a couple of hours to set
> up myself.
Have you asked on builds@ or filed an INFRA Jira issue or asked on #asfinf
On Sun, Jun 2, 2013 at 9:01 AM, Alejandro Abdelnur wrote:
> [...] an easy way to solve it it would be using as release date the date the
> vote ends.
+1 This is what I've done for release candidate builds.
Doug
On Thu, May 2, 2013 at 11:29 AM, Colin McCabe wrote:
> It seems like we could just set up an escape sequence and make it actually
> binary-safe, rather than just probabilistically.
That would require a scan of data as it's written & read, which has
performance implications.
Doug
wrote:
>
>> Taking silence here to mean we aren't that concerned with the javadocs.
>>
>> Are we okay with Doug's proposed fix for the broken links?
>>
>> Thanks,
>> Andrew
>>
>>
>> On Thu, Feb 14, 2013 at 4:06 PM, Doug Cutting
All of Hadoop's javadocs were recently lost from our website when it
was converted to svnpubsub. These were historically not stored in
subversion but manually added to the website by release managers.
When the site was converted to svnpubsub no one had first copied the
docs tree into subversion so
On Tue, Aug 7, 2012 at 5:52 AM, Apurv Verma wrote:
> why was it decided to declare them as
>
> public class IntWritable implements WritableComparable
>
> and not as
>
> public class IntWritable implements WritableComparable
This class was written in 2003. Generics were added to Java in 2004.
Do
On 03/28/2012 12:39 PM, Owen O'Malley wrote:
> [ ... ] So the RM of the 2 branch needs to make the call of what
> should be 2.1 vs 3.0.
I thought these were community decisions, not RM decisions, no?
http://s.apache.org/rm
Doug
On 10/27/2011 10:47 AM, Suresh Srinivas wrote:
> Following issues need to be ported from trunk to 0.23.
>
> HADOOP-2298 TestDFSOverAvroRpc fails
> Justification: This makes a protocol method name change. Required for
> compatibility of 0.23 with future releases.
> Risk: low
Note this requires tha
On 10/03/2011 02:50 PM, Todd Lipcon wrote:
> 2) Move the branch itself into some kind of attic/ directory
We might:
1. Let it lie, alongside other dead branches like branch-0.1, etc.
2. Create a directory for dead branches and move all of the dead
branches there.
3. Remove all dead branches.
I
[
https://issues.apache.org/jira/browse/HDFS-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting resolved HDFS-1077.
Resolution: Duplicate
Resovling this as a duplicate of HDFS-2298.
Note that, with HADOOP-7693
A smaller checksum interval decreases the overhead for random access.
If one seeks to a random location, one must, on average, read and
checksum an extra checksumInterval/2 bytes. 512 was chosen as a value
that, with four-byte CRC32, reduced the impact on small seeks while
increasing the storage a
Suresh, Sanjay,
Thank you very much for addressing my questions.
Cheers,
Doug
On 04/26/2011 10:29 AM, suresh srinivas wrote:
> Doug,
>
>
>> 1. Can you please describe the significant advantages this approach has
>> over a symlink-based approach?
>
> Federation is complementary with symlink a
On 04/22/2011 09:48 AM, Suresh Srinivas wrote:
> A few weeks ago, I had sent an email about the progress of HDFS
> federation development in HDFS-1052 branch. I am happy to announce
> that all the tasks related to this feature development is complete
> and it is ready to be integrated into trunk.
On 08/19/2010 05:32 PM, Tsz Wo (Nicholas), Sze wrote:
Do we need a vote for creating a development branch?
I don't think a vote is required. I agree that any committer should be
able to create a branch.
Note however, that, if a committer were to wish to create a branch that
alters, e.g., t
-node
Reporter: Doug Cutting
Assignee: Doug Cutting
Avro RPC does not permit two different messages with the same name. Several
namenode RPC protocol method names are overloaded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a
: Doug Cutting
Assignee: Doug Cutting
Some HDFS command-line tests (TestHDFSCLI) fail when using AvroRpcEngine
because the error string does not match. Calling getMessage() on a remote
exception thrown by WritableRpcEngine produces a string that contains the
exception name followed by
Make HDFS tests pass using Avro RPC
---
Key: HDFS-1066
URL: https://issues.apache.org/jira/browse/HDFS-1066
Project: Hadoop HDFS
Issue Type: Bug
Components: name-node
Reporter: Doug
: Doug Cutting
Assignee: Doug Cutting
Fix For: 0.22.0
It should be possible to configure HDFS so that Avro is used for RPCs to the
namenode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
22 matches
Mail list logo
