[jira] Created: (PIG-1711) Document BinStorage behaviour

Document BinStorage behaviour -- Key: PIG-1711 URL: https://issues.apache.org/jira/browse/PIG-1711 Project: Pig Issue Type: Bug Components: documentation Affects Versions: 0.7.0, 0.6.0 R

[jira] Commented: (PIG-1693) There needs to be a way in foreach to indicate "and all the rest of the fields"

[ https://issues.apache.org/jira/browse/PIG-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928900#action_12928900 ] Scott Carey commented on PIG-1693: -- If this doesn't work with named aliases, its almost usel

[jira] Commented: (PIG-1112) FLATTEN eliminates the alias

[ https://issues.apache.org/jira/browse/PIG-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928889#action_12928889 ] Alan Gates commented on PIG-1112: - Daniel, I don't understand the choice here. I think we ag

[jira] Commented: (PIG-1341) BinStorage cannot convert DataByteArray to Chararray and results in FIELD_DISCARDED_TYPE_CONVERSION_FAILED

[ https://issues.apache.org/jira/browse/PIG-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928887#action_12928887 ] Alan Gates commented on PIG-1341: - We can mark BinStorage as deprecated if we want, though I

[jira] Commented: (PIG-1341) BinStorage cannot convert DataByteArray to Chararray and results in FIELD_DISCARDED_TYPE_CONVERSION_FAILED

[ https://issues.apache.org/jira/browse/PIG-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928884#action_12928884 ] Viraj Bhat commented on PIG-1341: - Hi Alan, I think we should stop exposing BinStorage to us

[jira] Updated: (PIG-1710) Document limitation on how many aliases cogroup can handle and why users should not cogroup more than 127 aliases

[ https://issues.apache.org/jira/browse/PIG-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Bhat updated PIG-1710: Description: We have a usecase in Pig where we cogroup on more than 2000 aliases. {code} cogroup_1 = foreach

[jira] Updated: (PIG-1710) Document limitation on how many aliases cogroup can handle and why users should not cogroup more than 127 aliases

[ https://issues.apache.org/jira/browse/PIG-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Bhat updated PIG-1710: Description: We have a usecase in Pig where we cogroup on more than 2000 aliases. {code} cogroup_1 = foreach

[jira] Updated: (PIG-1710) Document limitation on how many aliases cogroup can handle and why users should not cogroup more than 127 aliases

[ https://issues.apache.org/jira/browse/PIG-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Bhat updated PIG-1710: Description: We have a usecase in Pig where we cogroup on more than 2000 aliases. {code} cogroup_1 = foreach

[jira] Created: (PIG-1710) Document limitation on how many aliases cogroup can handle and why users should not cogroup more than 127 aliases

Document limitation on how many aliases cogroup can handle and why users should not cogroup more than 127 aliases - Key: PIG-1710 URL: https://issues.a

[jira] Commented: (PIG-1709) Skewed join use fewer reducer for extreme large key

[ https://issues.apache.org/jira/browse/PIG-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928869#action_12928869 ] Daniel Dai commented on PIG-1709: - As Thejas point out, the right approach and original desig

[jira] Updated: (PIG-1305) Document in Load statement syntax that Pig and underlying M/R does not handle concatenated bz2 and gz files correctly

[ https://issues.apache.org/jira/browse/PIG-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Bhat updated PIG-1305: Fix Version/s: (was: 0.7.0) 0.9.0 > Document in Load statement syntax that Pig and un

[jira] Updated: (PIG-1304) Fail underlying M/R jobs when concatenated gzip and bz2 files are provided as input

[ https://issues.apache.org/jira/browse/PIG-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Bhat updated PIG-1304: Fix Version/s: 0.9.0 > Fail underlying M/R jobs when concatenated gzip and bz2 files are provided as > input

[jira] Commented: (PIG-749) No attempt to check if 'flatten(group) as' has the same cardinality as 'group alias by'

[ https://issues.apache.org/jira/browse/PIG-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928840#action_12928840 ] Daniel Dai commented on PIG-749: In the current code, it fails, but error message need to impr

[jira] Commented: (PIG-1112) FLATTEN eliminates the alias

[ https://issues.apache.org/jira/browse/PIG-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928837#action_12928837 ] Daniel Dai commented on PIG-1112: - In current trunk, the schema for B becomes: B: {first: cha

Re: Switching join operators based on data properties

yes on LoadMetadata being how the user provides the data, and yes on only attaching to logical operators. D On Fri, Nov 5, 2010 at 10:38 AM, Renato Marroquín Mogrovejo < renatoj.marroq...@gmail.com> wrote: > @Gianmarco > It would be in a way. A cost based optimizer would be awesome, but when > d

[jira] Created: (PIG-1709) Skewed join use fewer reducer for extreme large key

Skewed join use fewer reducer for extreme large key --- Key: PIG-1709 URL: https://issues.apache.org/jira/browse/PIG-1709 Project: Pig Issue Type: Bug Components: impl Affects Ver

[jira] Updated: (PIG-1341) BinStorage cannot convert DataByteArray to Chararray and results in FIELD_DISCARDED_TYPE_CONVERSION_FAILED

[ https://issues.apache.org/jira/browse/PIG-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated PIG-1341: Resolution: Won't Fix Status: Resolved (was: Patch Available) > BinStorage cannot convert DataByteAr

[jira] Created: (PIG-1708) Cross after Limit produces wrong results

Cross after Limit produces wrong results Key: PIG-1708 URL: https://issues.apache.org/jira/browse/PIG-1708 Project: Pig Issue Type: Bug Affects Versions: 0.7.0 Reporter: Anil Chawla

[jira] Resolved: (PIG-696) Fatal error produced when malformed scalar types within complex type is converted to given type

[ https://issues.apache.org/jira/browse/PIG-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai resolved PIG-696. Resolution: Fixed Verified already fixed in trunk. > Fatal error produced when malformed scalar types within

Re: Switching join operators based on data properties

@Gianmarco It would be in a way. A cost based optimizer would be awesome, but when dealing with large amounts of data, important things such as statistics to make accurate estimations are not that easy to get or to maintain. And about just hacking into the code, I guess it is my fault for not expla

Build failed in Hudson: Pig-trunk #859

See Changes: [nigel] Update hudson patch admin script to fix missing option -- [...truncated 2518 lines...] [ivy:resolve] found org.apache.ftpserver#ftpserver-deprecated;1.0.0-M2 in default [i

Build failed in Hudson: Pig-trunk-commit #582

See Changes: [nigel] Update hudson patch admin script to fix missing option -- [...truncated 4979 lines...] [ivy:resolve] found commons-el#commons-el;1.0 in default [ivy:resolve] found

Build failed in Hudson: Pig-trunk #858

See Changes: [rding] update trunk verion to 0.9.0 -- [...truncated 2526 lines...] [ivy:resolve] found commons-lang#commons-lang;2.4 in default [ivy:resolve] found com.google.guava#guava;r06 i

pig LoadMetaData find schema in AS clause from Loader.

HI, Is there any way in Pig where a LoadFunc can retrieve the Schema definition entered by the user in the AS clause? e.g. A = LOAD '$INPUT' USING MyLoader() AS (a:int, b:int); My question comes from the below problem I'm facing: So I'm writing a Loader that adds partition fields