[jira] [Updated] (HIVE-18538) Updating last.repl.id on replica warehouse when dbName specified as a pattern
[ https://issues.apache.org/jira/browse/HIVE-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stamatis Zampetakis updated HIVE-18538: --- Fix Version/s: (was: 3.2.0) I cleared the fixVersion field since this ticket is still open. Please review this ticket and if the fix is already committed to a specific version please set the version accordingly and mark the ticket as RESOLVED. According to the [JIRA guidelines|https://cwiki.apache.org/confluence/display/Hive/HowToContribute] the fixVersion should be set only when the issue is resolved/closed. > 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 Agarwal >Assignee: Anishek Agarwal >Priority: Major > > 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 (v8.20.10#820010)
[jira] [Updated] (HIVE-18538) Updating last.repl.id on replica warehouse when dbName specified as a pattern
[ 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)
[jira] [Updated] (HIVE-18538) Updating last.repl.id on replica warehouse when dbName specified as a pattern
[ 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.0.0) 3.1.0 Deferring this to 3.1.0 since the branch for 3.0.0 has been cut off. Please update the JIRA if you would like to get your patch in 3.0.0. > 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.1.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)
[jira] [Updated] (HIVE-18538) Updating last.repl.id on replica warehouse when dbName specified as a pattern
[ https://issues.apache.org/jira/browse/HIVE-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] anishek updated HIVE-18538: --- Description: 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 (was: 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 rethink this feature. ) > 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 >Priority: Major > Fix For: 3.0.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)
[jira] [Updated] (HIVE-18538) Updating last.repl.id on replica warehouse when dbName specified as a pattern
[ https://issues.apache.org/jira/browse/HIVE-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] anishek updated HIVE-18538: --- Summary: Updating last.repl.id on replica warehouse when dbName specified as a pattern (was: Updating last.repl.id on replica warehouse with db patterns now allowed ) > 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 >Priority: Major > Fix For: 3.0.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 rethink > this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
