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] [Updated] (HIVE-19116) Vectorization: Vector Map data type doesn't keep the order of the key/values pairs as read
Date Fri, 06 Apr 2018 14:59:00 GMT

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

Matt McCline updated HIVE-19116:
--------------------------------
    Fix Version/s: 3.0.0

> Vectorization: Vector Map data type doesn't keep the order of the key/values pairs as
read
> ------------------------------------------------------------------------------------------
>
>                 Key: HIVE-19116
>                 URL: https://issues.apache.org/jira/browse/HIVE-19116
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 3.0.0
>            Reporter: Matt McCline
>            Assignee: Matt McCline
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: HIVE-19116.01.patch
>
>
> The VectorExtractRow class does not preserve the order of the key/value pairs when going
from MapColumnVector to a Map object.  This causes Q file differences in tests with the MAP
data type making it seem like we are getting Wrong Results (well, actually we are).
> When LazyMap class (for example) adds key/value pairs to its "map" it uses a LinkedHashSet
to preserve insert order.
> FYI: [~teddy.choi]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message