[
https://issues.apache.org/jira/browse/HIVE-21788?focusedWorklogId=443120&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-443120
]
ASF GitHub Bot logged work on HIVE-21788:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jun/20 16:33
Start Date: 09/Jun/20 16:33
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on pull request #666:
URL: https://github.com/apache/hive/pull/666#issuecomment-640955875
This pull request has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the [email protected] list if the patch is in
need of reviews.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 443120)
Time Spent: 20m (was: 10m)
> Support replication from haddop-2 (hive 3.0 and beelow) on-prem cluster to
> hadoop-3 (hive 4 and above) cloud cluster
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-21788
> URL: https://issues.apache.org/jira/browse/HIVE-21788
> Project: Hive
> Issue Type: Task
> Components: HiveServer2, repl
> Affects Versions: 4.0.0
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21788.01.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In case of replication to cloud both dump and load are executed in the source
> cluster. This push based replication is done to avoid computation at target
> cloud cluster. In case in the source cluster, strict managed table is not set
> to true the tables will be non acid. So during replication to a cluster with
> strict managed table, migration logic same as upgrade tool has to be applied
> on the replicated data. This migration logic is implemented only in hive4.0.
> So it's required that a hive 4.0 instance started at the source cluster. If
> the source cluster has hadoop-2 installation, hive4 has to be built with
> hadoop-2 and necessary changes are required in the pom files and the shim
> files.
> 1. Change the pom.xml files to accept a profile for hadoop-2. If hadoop-2
> profile is set, the hadoop version should be set accordingly to hadoop-2.
> 2. In shim creare a new file for hadoop-2. Based on the profile the
> respective file will be included in the build.
> 3. Changed artifactId hadoop-hdfs-client to hadoop-client as in hadoop-2 the
> jars are stored under hadoop-client folder.
>
>
> Command to enable hadop-2 dependency — mvn clean install package
> -DskipTests -Pdist -pl '!standalone-metastore, !llap-common, !llap-client,
> !llap-ext-client, !llap-tez, !llap-server, !hbase-handler, !service, !hplsql,
> !kryo-registrator' -Phadoop-2.7
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
