You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Phabricator (JIRA)" <ji...@apache.org> on 2012/12/05 08:34:58 UTC

[jira] [Updated] (HIVE-3772) Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin)

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

Phabricator updated HIVE-3772:
------------------------------

    Attachment: D7155.1.patch

mbautin requested code review of "[jira] [HIVE-3772] Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin)".
Reviewers: ashutoshc, njain, raghotham, JIRA

  Reynold Xin's patch needed by the Shark project. https://github.com/amplab/hive/commit/17e1c3dd2f6d8eca767115dc46d5a880aed8c765
  (writeVLong should not use a static field due to concurrency concerns.)

TEST PLAN
  Unit tests

REVISION DETAIL
  https://reviews.facebook.net/D7155

AFFECTED FILES
  serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryUtils.java

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/16935/

To: ashutoshc, njain, raghotham, JIRA, mbautin

                
> Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin)
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-3772
>                 URL: https://issues.apache.org/jira/browse/HIVE-3772
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Mikhail Bautin
>         Attachments: D7155.1.patch
>
>
> Creating a JIRA for [~rxin]'s patch needed by the Shark project. https://github.com/amplab/hive/commit/17e1c3dd2f6d8eca767115dc46d5a880aed8c765
> writeVLong should not use a static field due to concurrency concerns.

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