Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # general >> Defining Hadoop Compatibility -revisiting-


Copy link to this message
-
Re: Defining Hadoop Compatibility -revisiting-
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 <[EMAIL PROTECTED]> 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?
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB