Yeah, sure, as soon as we all quit our respective jobs and start a support company :)
(on a more serious note, improving the error messages is a big item for Pig 0.9) (also, good god, 60k line Pig script. Look into workflow management tools that allow you to avid creating such monoliths). On Wed, Sep 29, 2010 at 8:18 PM, hc busy <hc.b...@gmail.com> wrote: > "null" was the error. this 60k PigLatin script that I'm running hasn't > changed that much, but suddenly started erroring out. I've rebuilt pig > release 7 from scratch, checked java version, err... checked PiggyBank and > our own libraries, not there changed. > > You know, some comercial software that has professional support will > actually send emails when an "unhandled error" occurs. The email is > received > by the developer/support and diagnosed. And in that email, it would contain > all the gory details that the product doesn't want to display to the user. > > > I wonder if you guys are up to doing something like that for pig? > > > > On Wed, Sep 29, 2010 at 8:13 PM, Jeff Zhang <zjf...@gmail.com> wrote: > > > No other stack trace ? And in what situation does this happen ? > > > > > > > > On Thu, Sep 30, 2010 at 11:09 AM, hc busy <hc.b...@gmail.com> wrote: > > > Guys, I'm seeing this one > > > > > > 2998 > > > > > > Unexpected internal error. > > > > > > > > > Can we be more specific or dump a stack trace when this happens? > > > > > > > > > > > -- > > Best Regards > > > > Jeff Zhang > > >
