hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vineet Garg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-18538) Updating last.repl.id on replica warehouse when dbName specified as a pattern
Date Wed, 27 Jun 2018 18:31:03 GMT

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

Vineet Garg updated HIVE-18538:
-------------------------------
    Fix Version/s:     (was: 3.1.0)
                   3.2.0

Deferring this to 3.2.0 since the branch for 3.1.0 has been cut off.

> Updating last.repl.id on replica warehouse when dbName specified as a pattern
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-18538
>                 URL: https://issues.apache.org/jira/browse/HIVE-18538
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: anishek
>            Assignee: anishek
>            Priority: Major
>             Fix For: 3.2.0
>
>
> Currently for bootstrap load we dynamically generate the task DAG at runtime rather than
generate the whole task graph at compile / semantic analysis time. The number of vertex as
part of this DAG is controlled via "hive.repl.approx.max.load.tasks".  Till now we only have
tested with replication with one database and providing the destination database name in the
repl load command, the ability to update the last.repl.id is dependent on this. Given we want
to move to a db regex for dumping data we have to relook at this implementation



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

Mime
View raw message