hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Szita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19944) Investigate and fix version mismatch of GCP
Date Wed, 27 Jun 2018 08:24:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-19944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524759#comment-16524759
] 

Adam Szita commented on HIVE-19944:
-----------------------------------

[~vihangk1], thanks for taking care and deleting that test image.

Just to explain this once again: this jira is not causing the issue - quite the contrary
it actually proposes to fix it.

As I was explaining in the summary part (and also internally before..) adding new images to
the project can break ptest if we try to restart it. This is because jclouds 2.0.0 reads all
images and expects "archiveSizeBytes" field to be present - which for new images it's not...
So I went ahead and started testing jclouds 2.1.0 on our test ptest server (obviously I needed
a new test image, which you have found and deleted) since in that release archiveSizeBytes
became nullable/optional.

Unfortunately since this patch was not committed and deployed yet, ptest failed to restart
with my test-image being present. Once this is committed (and I only need a review :) )
we'll be able to add new images to our ptest gcp project which allows your docker image work
to be continued.

 

> Investigate and fix version mismatch of GCP
> -------------------------------------------
>
>                 Key: HIVE-19944
>                 URL: https://issues.apache.org/jira/browse/HIVE-19944
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Adam Szita
>            Assignee: Adam Szita
>            Priority: Major
>         Attachments: HIVE-19944.0.patch
>
>
> We've observed that adding a new image to the ptest GCP project breaks our currently
working infrastructure when we try to restart the hive ptest server.
> This is because upon initialization the project's images are queried and we immediately
get an exception for newly added images - they don't have a field that our client thinks should
be mandatory to have. I believe there's an upgrade needed on our side for the GCP libs we
depend on.



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

Mime
View raw message