[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020251#comment-14020251 ] Daniel Dai commented on PIG-2597: - [~kyunghoj], besides "register" and "parameter substitution" PIG-3359 addresses, grunt shell commands does not support. Also the implementation of PIG-3359 is more a walk around. It is better to refactor it to fully integrate the "register" command into QueryParser. > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019544#comment-14019544 ] Kyungho Jeon commented on PIG-2597: --- Sorry that I hasn't been quite active. :( I think I am confused with the above comment by [~daijy] regarding Macro. I find a test case in the workaround (PIG-3359). Would it be good enough for me to design based on the test case, or is there any other cases that the test case does not cover? > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940976#comment-13940976 ] Daniel Dai commented on PIG-2597: - [~kyunghoj], Glad you reviewed the patch already. Yes, it's not just moving GruntParser from javacc to antlr, it also merging it into QueryParser. > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940665#comment-13940665 ] Kyungho Jeon commented on PIG-2597: --- [~daijy] I review the patch (PIG-3359). It seems that what needs to be done is to merge all language processing parts into a single one and to implement it with antlr. I will revise my proposal according to this, but it seems it's going to be a bigger project than I imagined from the title "Move grunt from javacc to antlr". > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938224#comment-13938224 ] Kyungho Jeon commented on PIG-2597: --- Thank you [~daijy]. I was not aware of the issue with Macro. I will look into the issue and update the proposal. > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936422#comment-13936422 ] Daniel Dai commented on PIG-2597: - Thanks [~kyunghoj], the proposal looks good. Another motivation to move javacc to ANTLR is we want to use all commands in Macro. There exist some workaround (PIG-3359). After this work, we need to clean up the workaround and make sure all commands works in Macro. > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934604#comment-13934604 ] Kyungho Jeon commented on PIG-2597: --- This is my initial draft: https://github.com/kyunghoj/GSoC2014 I am not sure how much details should be in design section. Also, I realized that other components based on JavaCC (e.g., Parameter substitution) might be bigger beasts. Should those component be included in this project? > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931571#comment-13931571 ] Daniel Dai commented on PIG-2597: - [~kyunghoj], thanks for your interest. If I get multiple proposals, I will have to pick the best one unless another mentor other than me is also interested in mentoring this. You can post either your entire proposal or a link to your proposal on Jira, so I can preview it before you submit to melange. > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930390#comment-13930390 ] Kyungho Jeon commented on PIG-2597: --- [~daijy] I am wondering what would happen if there are multiple applicants on the same project I am working on a proposal draft, so I don't want to waste my effort. ;) Could you review my proposal if I send it to you or post here? Thanks! > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925567#comment-13925567 ] Daniel Dai commented on PIG-2597: - [~vimuth], I should be available to mentor this. > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney >Assignee: Daniel Dai > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925419#comment-13925419 ] Vimuth commented on PIG-2597: - Hi, Im a third year computer science student from the university of moratuwa. Im interested in taking this on as my gsoc project. I've already checked out the code and built it and taken a quick look at the grunt related code. I'm currently following the tutorials provided in the gsoc getting started page Is there any possible mentors for this project so that i can discuss how to proceed further? > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney > Labels: gsoc2014 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2014. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2014 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603583#comment-13603583 ] Koji Noguchi commented on PIG-2597: --- bq. Jonathan, any update on this? I'm interested in this status as well. Does Boski have a plan to continue working on this? > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney > Labels: GSoC2012 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2012. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2012 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-2597) Move grunt from javacc to ANTRL
[ https://issues.apache.org/jira/browse/PIG-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471948#comment-13471948 ] Russell Jurney commented on PIG-2597: - Jonathan, any update on this? > Move grunt from javacc to ANTRL > --- > > Key: PIG-2597 > URL: https://issues.apache.org/jira/browse/PIG-2597 > Project: Pig > Issue Type: Improvement >Reporter: Jonathan Coveney > Labels: GSoC2012 > Attachments: pig02.diff > > > Currently, the parser for queries is in ANTLR, but Grunt is still javacc. The > parser is very difficult to work with, and next to impossible to understand > or modify. ANTLR provides a much cleaner, more standard way to generate > parsers/lexers/ASTs/etc, and moving from javacc to Grunt would be huge as we > continue to add features to Pig. > This is a candidate project for Google summer of code 2012. More information > about the program can be found at > https://cwiki.apache.org/confluence/display/PIG/GSoc2012 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
