hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Sankar Sivarama Subramaniyan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-5336) HCatSchema.remove(HCatFieldSchema hcatFieldSchema) should renumber the fieldPositionMap and the fieldPositionMap should not be cached by the end user
Date Mon, 23 Sep 2013 20:35:03 GMT

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

Hari Sankar Sivarama Subramaniyan updated HIVE-5336:
----------------------------------------------------

    Status: Patch Available  (was: Open)
    
> HCatSchema.remove(HCatFieldSchema hcatFieldSchema) should renumber the  fieldPositionMap
and the fieldPositionMap should not be cached by the end user
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-5336
>                 URL: https://issues.apache.org/jira/browse/HIVE-5336
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Hari Sankar Sivarama Subramaniyan
>            Assignee: Hari Sankar Sivarama Subramaniyan
>         Attachments: HIVE-5336.1.patch.txt
>
>
> HCatSchema.remove currently does not renumber the fieldPositionMap which can be a problem
when there are interleaving append() and remove() calls.
> 1. We should document that fieldPositionMap should not be cached by the end-user
> 2. We should make sure that the fieldPositionMap gets renumbered after remove() because
HcatSchema.get will otherwise return wrong FieldSchemas.

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

Mime
View raw message