hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16591) DR for function Binaries on HDFS
Date Mon, 22 May 2017 14:21:04 GMT

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

Hive QA commented on HIVE-16591:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12869257/HIVE-16591.1.patch

{color:green}SUCCESS:{color} +1 due to 3 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 10744 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_if_expr] (batchId=144)
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/5383/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/5383/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-5383/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12869257 - PreCommit-HIVE-Build

> 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
>
>
> # 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)

Mime
View raw message