updated example

2011-10-11 Thread Keith Thompson
I see that the JobConf class used in the WordCount tutorial is deprecated
for the Configuration class.  I am wanting to change the file input format
(to the StreamInputFormat for XML as in Hadoop: The Definitive Guide pp.
212-213) but I don't see a setInputFormat method in the Configuration class
as there was in the JobConf class.  Is there an updated example using the
non-deprecated classes and methods?  I have searched but not found one.

Regards,
Keith


Re: updated example

2011-10-11 Thread Tom White
JobConf and the old API are no longer deprecated in the forthcoming
0.20.205 release, so you can continue to use it without issue.

The equivalent in the new API is setInputFormatClass() on
org.apache.hadoop.mapreduce.Job.

Cheers,
Tom

On Tue, Oct 11, 2011 at 9:18 AM, Keith Thompson kthom...@binghamton.edu wrote:
 I see that the JobConf class used in the WordCount tutorial is deprecated
 for the Configuration class.  I am wanting to change the file input format
 (to the StreamInputFormat for XML as in Hadoop: The Definitive Guide pp.
 212-213) but I don't see a setInputFormat method in the Configuration class
 as there was in the JobConf class.  Is there an updated example using the
 non-deprecated classes and methods?  I have searched but not found one.

 Regards,
 Keith



Re: updated example

2011-10-11 Thread Jignesh Patel
Thea means old API is not integrated in 0.20.204.0??

When do you expect the release of 0.20.205?

-Jignesh
On Oct 11, 2011, at 12:32 PM, Tom White wrote:

 JobConf and the old API are no longer deprecated in the forthcoming
 0.20.205 release, so you can continue to use it without issue.
 
 The equivalent in the new API is setInputFormatClass() on
 org.apache.hadoop.mapreduce.Job.
 
 Cheers,
 Tom
 
 On Tue, Oct 11, 2011 at 9:18 AM, Keith Thompson kthom...@binghamton.edu 
 wrote:
 I see that the JobConf class used in the WordCount tutorial is deprecated
 for the Configuration class.  I am wanting to change the file input format
 (to the StreamInputFormat for XML as in Hadoop: The Definitive Guide pp.
 212-213) but I don't see a setInputFormat method in the Configuration class
 as there was in the JobConf class.  Is there an updated example using the
 non-deprecated classes and methods?  I have searched but not found one.
 
 Regards,
 Keith
 



RE: updated example

2011-10-11 Thread GOEKE, MATTHEW (AG/1000)
The old API is still fully usable in 0.20.204.

Matt

-Original Message-
From: Jignesh Patel [mailto:jign...@websoft.com] 
Sent: Tuesday, October 11, 2011 12:17 PM
To: common-user@hadoop.apache.org
Subject: Re: updated example

Thea means old API is not integrated in 0.20.204.0??

When do you expect the release of 0.20.205?

-Jignesh
On Oct 11, 2011, at 12:32 PM, Tom White wrote:

 JobConf and the old API are no longer deprecated in the forthcoming
 0.20.205 release, so you can continue to use it without issue.
 
 The equivalent in the new API is setInputFormatClass() on
 org.apache.hadoop.mapreduce.Job.
 
 Cheers,
 Tom
 
 On Tue, Oct 11, 2011 at 9:18 AM, Keith Thompson kthom...@binghamton.edu 
 wrote:
 I see that the JobConf class used in the WordCount tutorial is deprecated
 for the Configuration class.  I am wanting to change the file input format
 (to the StreamInputFormat for XML as in Hadoop: The Definitive Guide pp.
 212-213) but I don't see a setInputFormat method in the Configuration class
 as there was in the JobConf class.  Is there an updated example using the
 non-deprecated classes and methods?  I have searched but not found one.
 
 Regards,
 Keith
 

This e-mail message may contain privileged and/or confidential information, and 
is intended to be received only by persons entitled
to receive such information. If you have received this e-mail in error, please 
notify the sender immediately. Please delete it and
all attachments from any servers, hard drives or any other media. Other use of 
this e-mail by you is strictly prohibited.

All e-mails and attachments sent and received are subject to monitoring, 
reading and archival by Monsanto, including its
subsidiaries. The recipient of this e-mail is solely responsible for checking 
for the presence of Viruses or other Malware.
Monsanto, along with its subsidiaries, accepts no liability for any damage 
caused by any such code transmitted by or accompanying
this e-mail or any attachment.


The information contained in this email may be subject to the export control 
laws and regulations of the United States, potentially
including but not limited to the Export Administration Regulations (EAR) and 
sanctions regulations issued by the U.S. Department of
Treasury, Office of Foreign Asset Controls (OFAC).  As a recipient of this 
information you are obligated to comply with all
applicable U.S. export laws and regulations.