[
https://issues.apache.org/jira/browse/HIVE-22525?focusedWorklogId=349497&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-349497
]
ASF GitHub Bot logged work on HIVE-22525:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Nov/19 01:50
Start Date: 26/Nov/19 01:50
Worklog Time Spent: 10m
Work Description: jcamachor commented on pull request #850: HIVE-22525
Refactor HiveOpConverter
URL: https://github.com/apache/hive/pull/850
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 349497)
Time Spent: 0.5h (was: 20m)
> Refactor HiveOpConverter
> ------------------------
>
> Key: HIVE-22525
> URL: https://issues.apache.org/jira/browse/HIVE-22525
> Project: Hive
> Issue Type: Improvement
> Components: Hive
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-22525.01.patch, HIVE-22525.02.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> HiveOpConverter is on it's way to become a monster class. It is already ~1300
> lines long, and expected to grow. It should be refactored, cut into multiple
> classes in a reasonable way. It is a natural way to do this is to create
> separate visitor classes for the different RelNodes, which are already
> handled in different functions within HiveOpConverter. That way
> HiveOpConverter can be the dispatcher among those visitor classes, while each
> of them are handling some specific work, potentially requesting sub nodes to
> be dispatched by HiveOpConverter. The functions used by multiple visitors
> should be put into some utility class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
