Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.8.0
-
None
-
None
Description
There are many bugs in Pig related to the parser, particularly to bad error messages. After review of Java CC we feel these will be difficult to address using that tool. Also, the .jjt files used by JavaCC are hard to understand and maintain.
ANTLR is being reviewed as the most likely choice to move to, but other parsers will be reviewed as well.
This JIRA will act as an umbrella issue for other parser issues.
Attachments
Attachments
Issue Links
- is blocked by
-
PIG-1622 DEFINE streaming options are ill defined and not properly documented
- Closed
- is depended upon by
-
PIG-217 Syntax Errors
- Open
-
PIG-394 Syntax for ?: requires parens in FOREACH
- Open
-
PIG-579 Adding newlines to format foreach statement with constants causes parse errors
- Open
-
PIG-838 Parser does not handle ctrl-m ('\u000d') as argument to PigStorage
- Open
-
PIG-900 ORDER BY syntax wrt parentheses is somewhat different than GROUP BY and FILTER BY
- Open
-
PIG-1339 International characters in column names not supported
- Open
-
PIG-19 A=load causes parse error
- Open
-
PIG-356 map lookup on empty key should be disallowed at parse time
- Open
-
PIG-377 Grunt parser doesn't handle escape codes correctly
- Open
-
PIG-548 ParseException involving "as" keyword
- Open
-
PIG-583 Bag constants used in non foreach statements cause lexical errors
- Open
-
PIG-1623 Register syntax is ambiguous
- Open
-
PIG-1663 Order by only allows ordering on columns, not expressions
- Open
-
PIG-731 Passing semicolon as a parameter in UDF causes parser error
- Resolved
-
PIG-596 Anonymous tuples in bags create ParseExceptions
- Closed
-
PIG-618 Bad error message when period rather than comma appears as separator in UDF parameter list
- Closed
-
PIG-1152 bincond operator throws parser error
- Closed
-
PIG-1462 No informative error message on parse problem
- Closed
-
PIG-1545 Secondary alias gives problem, when it has alias in the group by statement.
- Closed
-
PIG-1774 parser should not require bincond/conditional operator to be within parenthesis
- Closed
-
PIG-144 The error message should be more meaningful when there is a typo in PIg script
- Closed
-
PIG-670 DIFF contains an invalid expression - possible parser error
- Closed
-
PIG-674 Improve errors in Pig parser
- Closed
-
PIG-719 store <expr> into 'filename'; should be valid syntax, but does not work
- Closed
-
PIG-1092 Pig Latin Parser fails to recognize "\n" as a whitespace
- Closed
-
PIG-1581 Parser fails to recognize semicolons in quoted strings
- Closed
-
PIG-1619 Bad error message when a double constant is incorrectly specified
- Closed
-
PIG-1620 ARRANGE keyword should be deprecated
- Closed
-
PIG-1621 What does EVAL keyword do?
- Closed
-
PIG-1244 parameter syntax in scripts, add support for ${VAR} (in addition to current $VAR)
- Resolved
-
PIG-1499 Type error message does not include complex type
- Closed
-
PIG-1387 Syntactical Sugar for PIG-1385
- Closed