hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt McCline (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HIVE-16863) Vectorization: See if instanceof checks added to VectorAssignRow in HIVE-16589 can be removed...
Date Fri, 09 Jun 2017 00:50:19 GMT

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

Matt McCline reassigned HIVE-16863:
-----------------------------------


> Vectorization: See if instanceof checks added to VectorAssignRow in HIVE-16589 can be
removed...
> ------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-16863
>                 URL: https://issues.apache.org/jira/browse/HIVE-16863
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>            Reporter: Matt McCline
>            Assignee: Teddy Choi
>            Priority: Critical
>
> (Wait for HIVE-16589 commit).
> During HIVE-16589 when VectorUDFAdaptor was converted to use VectorAssignRow instead
of adding Complex Type variants to setOutputCol we added instanceof checks since data from
VectorUDFAdaptor is sometimes a Byte object instead of a ByteWritable, etc.
> In code review, Jason suggested we might be able to make use of the output object inspectors.
 Is there a way to add (perhaps) a 2nd method(s) that can take advantage of its object inspectors
and not do instanceof stuff?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message