I've only ever seen it the once, which is why it was so surprising and I thought worth mentioning.
2011/3/10 Daniel Dai <[email protected]> > PerformanceTimerFactory is bundled in pig.jar. I can't think of any reason > why Pig cannot find this class. Also the invoking code is in the main code > path, so every run will go over it. Do you see this error every time? Try do > a clean rebuild and run it again. > > Daniel > > > On 03/08/2011 12:13 PM, Jonathan Coveney wrote: > >> Here is my svn info >> >> URL: http://svn.apache.org/repos/asf/pig/trunk >> Repository Root: http://svn.apache.org/repos/asf >> Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 >> Revision: 1078842 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: thejas >> Last Changed Rev: 1078086 >> Last Changed Date: 2011-03-04 13:19:08 -0500 (Fri, 04 Mar 2011) >> >> >> 2011/3/8 Alan Gates<[email protected]> >> >> What version of Pig are you using? PerformanceTimerFactory should only >>> be >>> used in debugging code, it shouldn't be involved in a regular usage. >>> >>> Alan. >>> >>> >>> On Mar 8, 2011, at 6:50 AM, Jonathan Coveney wrote: >>> >>> I have a rather large query that took quite a while to execute >>> (11hours, >>> >>>> probably on the order of 70B rows), and while the job tracker website we >>>> have seems to indicate that the query finished, here is what I see in >>>> pig >>>> (around the 95% completion mark, and then the reporting simply died): >>>> >>>> Exception in thread "main" java.lang.NoClassDefFoundError: >>>> org/apache/pig/tools/timer/PerformanceTimerFactory >>>> at org.apache.pig.Main.run(Main.java:576) >>>> at org.apache.pig.Main.main(Main.java:108) >>>> Caused by: java.lang.ClassNotFoundException: >>>> org.apache.pig.tools.timer.PerformanceTimerFactory >>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >>>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >>>> ... 2 more >>>> >>>> While obviously I only care about getting my info (which seems fine and >>>> in >>>> tact), I thought it was worth mentioning that I saw this in case no one >>>> has >>>> run across the bug? Especially given that it's important to see bugs >>>> that >>>> come from actual use and not just local mode testing... >>>> >>>> >>> >
