[ 
https://issues.apache.org/jira/browse/TAJO-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830615#comment-13830615
 ] 

Min Zhou commented on TAJO-323:
-------------------------------

I am worried about sooner or later we will support subqueries.  Will make it 
more messy than present time :)
One alternative is that we can use Plan rather than Query, and consequently 
SubQuery be SubPlan. Just a suggestion, never mind 

Min

> Refactor inconsistent class and variable names
> ----------------------------------------------
>
>                 Key: TAJO-323
>                 URL: https://issues.apache.org/jira/browse/TAJO-323
>             Project: Tajo
>          Issue Type: Task
>            Reporter: Hyunsik Choi
>             Fix For: 0.8-incubating
>
>
> There are inconsistent class and variable names. For example, QueryUnit and 
> task are used in a  mixing way, and QueryUnitAttempt and taskattempt are used 
> in a  mixing way. They reduce readability and make developers confuse.
> Now is the right time to correct them. The main object of this issue is to 
> investigate those inconsistent class and variable names and correct them.
> However, this work may make many conflicts. In order to minimize the code 
> conflict, we need to make a number of small separate refactors.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to