beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4260) Document usage for hcatalog 1.1
Date Thu, 02 Aug 2018 08:54:00 GMT


ASF GitHub Bot logged work on BEAM-4260:

                Author: ASF GitHub Bot
            Created on: 02/Aug/18 08:53
            Start Date: 02/Aug/18 08:53
    Worklog Time Spent: 10m 
      Work Description: asfgit commented on issue #512: [BEAM-4260] Document HCatalogIO use
with Hive 1.1
   Error: PR failed in verification; check the Jenkins job for more information.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 130184)
    Time Spent: 1h 20m  (was: 1h 10m)

> Document usage for hcatalog 1.1
> -------------------------------
>                 Key: BEAM-4260
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-hcatalog, website
>    Affects Versions: 2.4.0
>            Reporter: Tim Robertson
>            Assignee: Tim Robertson
>            Priority: Minor
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> The {{HCatalogIO}} does not work with environments providing Hive Server 1.x which is
in widespread use - as an example the latest Cloudera (5.14.2) provides 1.1.x
> The {{HCatalogIO}} marks it's Hive dependencies as provided, so I believe the intention
was to be open to multiple versions.
> The issues come from the following:  
>  - use of {{HCatUtil.getHiveMetastoreClient(hiveConf)}} while previous versions used
the [now deprecated|]
{{getHiveClient(HiveConf hiveConf)}}  
>  - Changes to the signature of {{RetryingMetaStoreClient.getProxy(...)}}
> Given this doesn't work in a major Hadoop distro, and will not until the next CDH release
later in 2018 (i.e. widespread adoption only expected in 2019) I think it would be worthwhile
providing a fix/workaround.
> I _think_ building for 2.3 and relocating in your own app might be a workaround although
I'm still testing it.  If that is successful I'd propose adding it to the project README or
in a separate markdown file linked from the README.
> Does that sound like a reasonable approach please?

This message was sent by Atlassian JIRA

View raw message