Affects Version/s: None
Fix Version/s: 0.2.0
Pig and Grunt
If we can detect parse/lexical/syntax/etc. issues before running a script we can save user/cluster time. Occasionally this results in a long script failing in the middle because of a simple detectable typo and wasting time/processing power. This issue can serve as holder of several examples and levels we can tackle this.
There were some discussions regarding having save-points/check-points so script can resume from a failed point. That goes in a separate issue.
Please go ahead and add your examples.
|Parser should detect tuple field number problems when possible||Closed|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||0.2.0 [ 12313783 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|