[
https://issues.apache.org/jira/browse/HIVE-11212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947600#comment-14947600
]
Matt McCline commented on HIVE-11212:
-------------------------------------
Noticed the new ensureSize method -- growing a batch beyond
VectorizedRowBatch.DEFAULT_SIZE. -- to support the new ListColumnVector's
storing a range of elements. The current vectorized operators that currently
only support primitive do have some hard coded assumptions where they allocate
various arrays (usually copies of the selected array) as being no more than
DEFAULT_SIZE. This doesn't affect this patch, but we'll need to be wary when
we later try to make the vectorized operators support complex types.
I think DecimalColumnVector.setElement needs to check if the return result from
...getHiveDecimal(precision, scale) is null and mark the vector column entry as
null. I think in some cases that method returns null when the value doesn't
fit, etc.
I'm still trying to grok the flatten/unflatten stuff...
> Create vectorized types for complex types
> -----------------------------------------
>
> Key: HIVE-11212
> URL: https://issues.apache.org/jira/browse/HIVE-11212
> Project: Hive
> Issue Type: Sub-task
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Attachments: HIVE-11212.patch, HIVE-11212.patch, HIVE-11212.patch
>
>
> We need vectorized types for structs, maps, lists, and unions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
