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

Posted to dev@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2013/09/03 20:35:53 UTC

[jira] [Updated] (HIVE-4959) Vectorized plan generation should be added as an optimization transform.

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

Ashutosh Chauhan updated HIVE-4959:
-----------------------------------

       Resolution: Fixed
    Fix Version/s: vectorization-branch
           Status: Resolved  (was: Patch Available)

Committed this to trunk. Thanks, Jitendra! 

Instead of maintaining a static list of vectorizable operator and expressions in Vectorizer class, better way to do this is via adding an annotation on UDF and using that. We should do that in a follow-up jira.
                
> Vectorized plan generation should be added as an optimization transform.
> ------------------------------------------------------------------------
>
>                 Key: HIVE-4959
>                 URL: https://issues.apache.org/jira/browse/HIVE-4959
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: vectorization-branch
>
>         Attachments: HIVE-4959.1.patch, HIVE-4959.2.patch, HIVE-4959.3.patch
>
>
> Currently the query plan is vectorized at the query run time in the map task. It will be much cleaner to add vectorization as an optimization step.

--
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