[jira] [Resolved] (PIG-1969) Typechecking warnings are no longer displayed

[ https://issues.apache.org/jira/browse/PIG-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair resolved PIG-1969. Resolution: Fixed The warnings are being printed in trunk. > Typechecking warnings are no longer di

[jira] [Commented] (PIG-1917) NativeMapReduce does not Allow Configuration Parameters containing Spaces

[ https://issues.apache.org/jira/browse/PIG-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017219#comment-13017219 ] Thejas M Nair commented on PIG-1917: To avoid breaking backward compatibility while supp

[jira] [Commented] (PIG-1917) NativeMapReduce does not Allow Configuration Parameters containing Spaces

[ https://issues.apache.org/jira/browse/PIG-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017197#comment-13017197 ] Thejas M Nair commented on PIG-1917: The pig parser is parsing the argument "-Dmapred.ch

[jira] [Commented] (PIG-1848) Confusing statement for Merge Join -> Both Conditions in Pig reference manual1

[ https://issues.apache.org/jira/browse/PIG-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017193#comment-13017193 ] Olga Natkovich commented on PIG-1848: - Indeed the section makes very little sense. Cor

[jira] [Assigned] (PIG-1848) Confusing statement for Merge Join -> Both Conditions in Pig reference manual1

[ https://issues.apache.org/jira/browse/PIG-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olga Natkovich reassigned PIG-1848: --- Assignee: Corinne Chandel (was: Olga Natkovich) > Confusing statement for Merge Join -> Both C

[jira] [Created] (PIG-1978) Secondary sort fail when dereferencing two fields inside foreach

Secondary sort fail when dereferencing two fields inside foreach Key: PIG-1978 URL: https://issues.apache.org/jira/browse/PIG-1978 Project: Pig Issue Type: Bug Compon

[jira] [Created] (PIG-1977) "Stream closed" error while reading Pig temp files (results of intermediate jobs)

"Stream closed" error while reading Pig temp files (results of intermediate jobs) - Key: PIG-1977 URL: https://issues.apache.org/jira/browse/PIG-1977 Project: Pig

[jira] [Created] (PIG-1976) One more TwoLevelAccess to remove

One more TwoLevelAccess to remove - Key: PIG-1976 URL: https://issues.apache.org/jira/browse/PIG-1976 Project: Pig Issue Type: Bug Components: impl Affects Versions: 0.9.0 Reporter: D

[jira] [Commented] (PIG-1971) New Logical Plan messes up schemas in projections

[ https://issues.apache.org/jira/browse/PIG-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017133#comment-13017133 ] Dmitriy V. Ryaboy commented on PIG-1971: 0.8, though if it is indeed a problem with

[jira] [Commented] (PIG-1971) New Logical Plan messes up schemas in projections

[ https://issues.apache.org/jira/browse/PIG-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017127#comment-13017127 ] Olga Natkovich commented on PIG-1971: - which release should this go to? 0.8? 0.9? > New

[jira] [Commented] (PIG-1971) New Logical Plan messes up schemas in projections

[ https://issues.apache.org/jira/browse/PIG-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017125#comment-13017125 ] Dmitriy V. Ryaboy commented on PIG-1971: Thanks for the fast response Daniel, I'll a

[jira] [Updated] (PIG-1963) in nested foreach, accumutive udf taking input from order-by does not get results in order

[ https://issues.apache.org/jira/browse/PIG-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated PIG-1963: --- Fix Version/s: 0.8.0 0.9.0 > in nested foreach, accumutive udf taking input from ord

[jira] [Resolved] (PIG-1948) java.lang.ClassCastException while using double value from result of a group

[ https://issues.apache.org/jira/browse/PIG-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair resolved PIG-1948. Resolution: Invalid The udf in this case was returning a map which had double as key, which is not s

[jira] [Updated] (PIG-1971) New Logical Plan messes up schemas in projections

[ https://issues.apache.org/jira/browse/PIG-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-1971: Attachment: PIG-1971-0.patch This is because HBaseStorage.pushProjection change requiredFieldList. requiredF

[jira] [Updated] (PIG-1963) in nested foreach, accumutive udf taking input from order-by does not get results in order

[ https://issues.apache.org/jira/browse/PIG-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated PIG-1963: --- Attachment: PIG-1963.1.patch PIG-1963.1.patch - unit tests, test-patch with 0.8 branch. Running them fo

[jira] [Updated] (PIG-1777) LoadFunc in a scripting language

[ https://issues.apache.org/jira/browse/PIG-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Meagher updated PIG-1777: -- Fix Version/s: (was: 0.9.0) 0.10 > LoadFunc in a scripting language >

[jira] [Commented] (PIG-1777) LoadFunc in a scripting language

[ https://issues.apache.org/jira/browse/PIG-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016834#comment-13016834 ] John Meagher commented on PIG-1777: --- I'm not actively working on it. I'm not sure what "f

Recall: Pig filter against flatten column

Badrinarayanan S would like to recall the message, "Pig filter against flatten column". Disclaimer: This message (including any attachments) is being sent from Fifth Generation Technologies India (P) Ltd. (5G) and may contain information that is proprietary, confidential and privileged. If you

Pig filter against flatten column

Hi, I am trying to run a filter against a column which is the result of a flatten operation. But the filter clause throws an exception as org.apache.pig.data.DataByteArray cannot be cast to java.lang.String. The exception is against the line doing the matches filter. If I change matches to eq