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
MapReduce >> mail # user >> Re: What is the preferred way to pass a small number of configuration parameters to a mapper or reducer


Copy link to this message
-
Re: What is the preferred way to pass a small number of configuration parameters to a mapper or reducer
A is the best way if it is considerably small ... had it been something
like all the parameters together make up a GB of data ... Then distributed
cache could have been a better option.
Custom input for key value pairs is out of scope as it might be difficult
to satisfy all your requirements.
On Sunday, December 30, 2012, Hemanth Yamijala wrote:

> If it is a small number, A seems the best way to me.
>
> On Friday, December 28, 2012, Kshiva Kps wrote:
>
>
> Which one is current ..
>
>
> What is the preferred way to pass a small number of configuration
> parameters to a mapper or reducer?
>
>
>
>
>
> *A.  *As key-value pairs in the jobconf object.
>
> * *
>
> *B.  *As a custom input key-value pair passed to each mapper or reducer.
>
> * *
>
> *C.  *Using a plain text file via the Distributedcache, which each mapper
> or reducer reads.
>
> **
>
>

--
Sent from iPhone
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