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

Posted to dev@hive.apache.org by "Matt McCline (JIRA)" <ji...@apache.org> on 2018/04/05 08:27:01 UTC

[jira] [Created] (HIVE-19116) Vectorization: Vector Map data type doesn't keep the order of the key/values pairs as read

Matt McCline created HIVE-19116:
-----------------------------------

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


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)