hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <tdunn...@maprtech.com>
Subject Re: Defining Hadoop Compatibility -revisiting-
Date Thu, 12 May 2011 04:37:56 GMT
As a specific example of how these are important, over in Mahout-land we
have been wrestling with determining just what it means to have dependencies
in the lib directory inside a jar.  This isn't documented, behaves
differently in different versions of Hadoop and means that some Mahout
programs work sometimes, but fail in high-profile locations like Twitter.

On Wed, May 11, 2011 at 7:26 PM, M. C. Srivas <mcsrivas@gmail.com> wrote:

> Such specifications are vitally important when
> implementing libraries like Cascading, Mahout, etc. For example, an
> application might open a file using the new API, and pass that stream into
> a
> library that manipulates the stream using some of the old API ... what is
> then the expectation of the state of the stream when the library call
> returns?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message