[
https://issues.apache.org/jira/browse/HIVE-16591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025896#comment-16025896
]
ASF GitHub Bot commented on HIVE-16591:
---------------------------------------
GitHub user anishek opened a pull request:
https://github.com/apache/hive/pull/189
HIVE-16591 : DR for function Binaries on HDFS
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anishek/hive HIVE-16591
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/189.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #189
----
commit c693d24820a0b99d7be0b971f1d473054afcd89f
Author: Anishek Agarwal <anis...@gmail.com>
Date: 2017-05-11T06:43:40Z
HIVE-16591 : DR for function Binaries on HDFS
----
> DR for function Binaries on HDFS
> ---------------------------------
>
> Key: HIVE-16591
> URL: https://issues.apache.org/jira/browse/HIVE-16591
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2
> Affects Versions: 3.0.0
> Reporter: anishek
> Assignee: anishek
> Attachments: HIVE-16591.1.patch, HIVE-16591.2.patch
>
>
> # We have to make sure that during incremental dump we dont allow functions
> to be copied if they have local filesystem "file://" resources. -- depends
> how much system side work we want to do, We are going to explicitly provide a
> caveat for replicating functions where in, only functions created "using"
> clause will be replicated and the "using" clause prohibits creating functions
> with the local "file://" resources and hence doing additional checks when
> doing repl dump might not be required.
> # We have to make sure that during the bootstrap / incremental dump we append
> the namenode host + port if functions are created without the fully
> qualified location of uri on hdfs, not sure how this would play for S3 or
> WASB filesystem.
> # We have to copy the binaries of a function resource list on CREATE / DROP
> FUNCTION . The change management file system has to keep a copy of the binary
> when a DROP function is called, to provide capability of updating binary
> definition for existing functions along with DR. An example of list of steps
> is given in doc (ReplicateFunctions.pdf ) attached in parent Issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
