[
https://issues.apache.org/jira/browse/HIVE-19944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522376#comment-16522376
]
Adam Szita commented on HIVE-19944:
-----------------------------------
Attached [^HIVE-19944.0.patch]. Bumping the jcloud version to 2.1.0 from 2.0.0
will bring us the fix for the mandatory/optional field (archiveSizeBytes)
problem.
See relevant jclouds change here:
[https://github.com/jclouds/jclouds/commit/715994b1254d32ebb2404f1ab0d302f21eab5118#diff-93dfc4dea1e9612412c1b5a8625bbae6R85]
I already started testing this by running a test ptest on two nodes, will
update the results here, but it's already a good sign that the application was
able to start, with jclouds 2.0.0 it was not...
> 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)
