hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Santhosh Srinivasan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-161) Rework physical plan
Date Wed, 28 May 2008 14:31:44 GMT

    [ https://issues.apache.org/jira/browse/PIG-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600487#action_12600487

Santhosh Srinivasan commented on PIG-161:

The following Physical Operators are missing:

1. PONot
2. POAnd
3. POOr
4. PORegexp
5. POCross (In the old code, POCross was re-written into foreach and cogroup)

Also, the Physical Operators assume that the Comparison Operator to be a Binary Expression
Operator. This assumption does not hold for PONot and POIsNull.

> Rework physical plan
> --------------------
>                 Key: PIG-161
>                 URL: https://issues.apache.org/jira/browse/PIG-161
>             Project: Pig
>          Issue Type: Sub-task
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>         Attachments: arithmeticOperators.patch, BinCondAndNegative.patch, CastAndMapLookUp.patch,
incr2.patch, incr3.patch, incr4.patch, incr5.patch, logToPhyTranslator.patch, MRCompilerTests_PlansAndOutputs.txt,
Phy_AbsClass.patch, physicalOps.patch, physicalOps.patch, physicalOps.patch, physicalOps.patch,
physicalOps_latest.patch, POCast.patch, POCast.patch, podistinct.patch, pogenerate.patch,
pogenerate.patch, pogenerate.patch, posort.patch, POUserFuncCorrection.patch, TEST-org.apache.pig.test.TestLocalJobSubmission.txt,
TEST-org.apache.pig.test.TestLogToPhyCompiler.txt, TEST-org.apache.pig.test.TestLogToPhyCompiler.txt,
TEST-org.apache.pig.test.TestMapReduce.txt, TEST-org.apache.pig.test.TestTypeCheckingValidator.txt,
TEST-org.apache.pig.test.TestUnion.txt, translator.patch, translator.patch, translator.patch,
> This bug tracks work to rework all of the physical operators as described in http://wiki.apache.org/pig/PigTypesFunctionalSpec

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message