[
https://issues.apache.org/jira/browse/HIVE-21770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894671#comment-16894671
]
Hive QA commented on HIVE-21770:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12976061/HIVE-21770.01.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 16693 tests
executed
*Failed tests:*
{noformat}
TestDataSourceProviderFactory - did not produce a TEST-*.xml file (likely timed
out) (batchId=232)
TestObjectStore - did not produce a TEST-*.xml file (likely timed out)
(batchId=232)
org.apache.hive.jdbc.miniHS2.TestMiniHS2.testConfInSession (batchId=286)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/18186/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/18186/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-18186/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 3 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12976061 - PreCommit-HIVE-Build
> Support extraction of replication spec from notification event.
> ----------------------------------------------------------------
>
> Key: HIVE-21770
> URL: https://issues.apache.org/jira/browse/HIVE-21770
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2, repl
> Affects Versions: 4.0.0
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21770.01.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The notification event structure currently does not have the partition spec.
> Events which can span across multiple databases and tables, the database and
> table info can not be obtained from the event structure. To know the event is
> added for which partition, the event message has to be deserialized and the
> partition information can be obtained from it.
> * Each event handler has to expose a static API.
> * The API should take the event as input and return the list of db name,
> table name and partition spec from it.
> * If database name, table name or partition name is present in the event
> structure, then return it. If all these info are present then no need to
> deserialize the message. Later if these info are added to the event structure
> then it will be useful.
> * Deserialize the message and create the list of name and return through a
> partition info class object.
> * If the table is not partitioned or is table level event, then set the
> partition info as null. Same for table info incase of db level events.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
