You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Raghotham Murthy (JIRA)" <ji...@apache.org> on 2008/12/18 03:14:44 UTC
[jira] Commented: (HIVE-185) fetch task code should be refactored
so that can be used somewhere else also
[ https://issues.apache.org/jira/browse/HIVE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657651#action_12657651 ]
Raghotham Murthy commented on HIVE-185:
---------------------------------------
Its better to just add to the FetchTask interface - boolean fetchObject(Vector<Object>) instead of moving all the logic to Utilities and passing around context objects. You can create a FetchTask with FetchWork for the map join functionality.
> fetch task code should be refactored so that can be used somewhere else also
> ----------------------------------------------------------------------------
>
> Key: HIVE-185
> URL: https://issues.apache.org/jira/browse/HIVE-185
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Namit Jain
> Attachments: patch.185.1
>
>
> fetch task code should be refactored so that can be used somewhere else also.
> Currently, fetch task has a lot of code to deal with reading a hive table (both partitioned and non-partitioned). That should be in some common location like utilities, so that it can be used by other components also.
> In case of map joins, similar functionality will be needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.