You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2013/09/23 06:39:02 UTC

[jira] [Updated] (TAJO-194) LogicalNode should have an identifier to distinguish each logical node instance.

     [ https://issues.apache.org/jira/browse/TAJO-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-194:
------------------------------

    Attachment: TAJO-194.patch

I've uploaded the patch.
                
> LogicalNode should have an identifier to distinguish each logical node instance.
> --------------------------------------------------------------------------------
>
>                 Key: TAJO-194
>                 URL: https://issues.apache.org/jira/browse/TAJO-194
>             Project: Tajo
>          Issue Type: Improvement
>          Components: planner/optimizer
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.2-incubating
>
>         Attachments: TAJO-194.patch
>
>
> In some parts of LogicalPlan, an instance object id is used as a key in some map data. If we have identifiers to distinguish each logical node instance, it would be better than the current implementation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira