Patrick Salami 2013-03-28, 19:51
Alan Gates 2013-03-29, 00:15
Patrick Salami 2013-03-29, 16:17
Koji Noguchi 2013-04-02, 17:27
With help from the reviewer, I learned that this was fixed in trunk.
but not in 0.11.
On Apr 2, 2013, at 1:27 PM, Koji Noguchi wrote:
Did it work with 0.11? If not, I hit a similar issue and created
Problem started from pig 0.10.
On Mar 29, 2013, at 12:17 PM, Patrick Salami wrote:
Thanks for the tip. We are actually using Pig 0.10. I will upgrade to 0.11
and see if that resolves the issue.
On Thu, Mar 28, 2013 at 5:15 PM, Alan Gates <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]><mailto:[EMAIL PROTECTED]>> wrote:
What version of Pig are you using? Unreasonably long parse times were in
issue in Pig 0.9 and 0.10, I believe those issues were fixed in Pig 0.11.
On Mar 28, 2013, at 12:51 PM, Patrick Salami wrote:
We have some very long pig scripts that run several times per day. We
believe that the script parsing process takes very long (about 1h).
this time, the pig command just hangs before any output is displayed (I
assuming this is the parsing phase). My question is, can this process be
optimized by somehow serializing the intermediate parsed script to disk
after the parsing phase is complete so that we don't have to go through
parsing process each time the script is run (so long as the script itself
does not change)? That way, we could then load and run the parsed
representation of the script rather than re-parsing it for each run.
this is probably not a readily-available feature, could someone please
point me to the right place in the code where this intermediate output
Patrick Salami 2013-04-03, 20:27