Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Pig >> mail # user >> Pig cannot resolve BamUDFLoader

Mehmet Belgin 2013-04-22, 21:06
j.barrett Strausser 2013-04-22, 21:20
Mehmet Belgin 2013-04-22, 21:54
j.barrett Strausser 2013-04-22, 22:09
Copy link to this message
RE: Pig cannot resolve BamUDFLoader
What is the .bam file your are trying to load as and how is it  generated?

What does your pig script look like? That will help answer your question.

-----Original Message-----
From: Mehmet Belgin [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2013 4:07 PM
Subject: Pig cannot resolve BamUDFLoader

Hi Everyone,

I have absolutely no experience with Pig and limited experience with hadoop, so please bear with me. We built a small hadoop cluster for experimental purposes and installed pig with all listed dependencies. I made sure that all of the jars are in CLASSPATH and env variables are defined as docuemtned, but still getting the following error:

2013-04-22 16:50:08,770 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 1070: Could not resolve BamUDFLoader using imports: [, org.apache.pig.builtin., org.apache.pig.impl.builtin.]

And this is the command we are running:

pig -param inputfile=./bowtie_sorted.bam -param outputfile=hadoop_bam.pileup -param pparallel=1 ${SEQPIG_HOME}/scripts/pileup.pig

My google search for this error or "BamUDFLoader" alone did not return anything useful. Which jar is supposed to provide this function? Any suggestions will be appreciated.

Thanks a lot in advance!

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.