[ 
https://issues.apache.org/jira/browse/HIVE-19249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444858#comment-16444858
 ] 

Thejas M Nair commented on HIVE-19249:
--------------------------------------

+1 pending tests.

I noticed that in master branch because of changes in HIVE-18238, every query 
already has a new HiveConf object. So we no longer need to create a new copy in 
ReplicationSemanticAnalyzer. This could be part of a follow up change (its not 
introduced by this patch).



> Replication: WITH clause is not passing the configuration to Task correctly 
> in all cases
> ----------------------------------------------------------------------------------------
>
>                 Key: HIVE-19249
>                 URL: https://issues.apache.org/jira/browse/HIVE-19249
>             Project: Hive
>          Issue Type: Bug
>          Components: repl
>    Affects Versions: 3.0.0, 3.1.0
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>            Priority: Major
>         Attachments: HIVE-19249.1.patch, HIVE-19249.2.patch
>
>
> When running repl load like following:
> {code}
> REPL LOAD `repldb_kms207` FROM 
> 'hdfs://url:8020/apps/hive/repl/f8b057a7-c3f2-43bd-8baa-f7408a9008fc' WITH 
> ('hive.exec.parallel'='true','hive.distcp.privileged.doAs'='beacon','hive.metastore.uris'='thrift://metastore-url:9083','hive.metastore.warehouse.dir'='s3a://s3-warehouse','hive.warehouse.subdir.inherit.perms'='false','hive.repl.replica.functions.root.dir'='s3a://s3-warehouse','fs.s3a.bucket.ss-datasets.endpoint'='s3-bucket-endpoint','fs.s3a.impl.disable.cache'='true','fs.s3a.server-side-encryption-algorithm'='SSE-KMS','fs.s3a.server-side-encryption.key'='encr-key','distcp.options.pp'='','distcp.options.pg'='','distcp.options.pu'='');
> {code}
> the task that get created need to use the configs that are passed in the 
> USING clause. However, in some cases the wrong config object gets used.



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

Reply via email to