We are actively rewriting the parser now. See https://issues.apache.org/jira/browse/PIG-1618
for details and progress. We don't set hard dates for releases this
far in advance, but we hope to have it out by April or May of 2011.
Alan.
On Dec 11, 2010, at 5:58 PM, Renato Marroquín
[
https://issues.apache.org/jira/browse/PIG-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yan Zhou updated PIG-1712:
--
Attachment: illustrator_6.patch
code cleanups, scalar fix, multi-query fix.
Pig Illustrate rework
[
https://issues.apache.org/jira/browse/PIG-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olga Natkovich updated PIG-1743:
Comment: was deleted
(was: Dear Sender,
I am currently OOO from December 6-10 without any access
+1
Ran the tutorial, ran some end-to-end tests in local mode and in a
cluster, built the docs, compiled everything.
Alan.
On Dec 13, 2010, at 12:01 PM, Olga Natkovich wrote:
Hi,
I have created a candidate build for Pig 0.8.0. A description of
what is new and different is included in
+1.
Tested the following items:
1. unit test
2. piggybank unit test
3. zebra nightly
4. harness tests
5. tutorial
All pass.
One minor concerns, in CHANGES.txt, 0.8 incompatible changes also
include PIG-1518: multi file input format for loaders. I don't think
we need to reroll release just
+1
Verified the md5 checksum.
Ran few local, MR mode queries.
Some unit tests
-Thejas
On 12/13/10 12:01 PM, Olga Natkovich ol...@yahoo-inc.com wrote:
Hi,
I have created a candidate build for Pig 0.8.0. A description of what is new
and different is included in the release notes:
[
https://issues.apache.org/jira/browse/PIG-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12971120#action_12971120
]
Richard Ding commented on PIG-1479:
---
Thanks Julien. How about the following proposal?
bq.
[
https://issues.apache.org/jira/browse/PIG-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12971182#action_12971182
]
Daniel Dai commented on PIG-1766:
-
The error is due to the conflict of two different uid
