[ https://issues.apache.org/jira/browse/HIVE-22068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912035#comment-16912035 ]
Hive QA commented on HIVE-22068: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12978133/HIVE-22068.07.patch {color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified. {color:green}SUCCESS:{color} +1 due to 16745 tests passed Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/18371/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/18371/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-18371/ 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 {noformat} This message is automatically generated. ATTACHMENT ID: 12978133 - PreCommit-HIVE-Build > Return the last event id dumped as repl status to avoid notification event > missing error. > ----------------------------------------------------------------------------------------- > > Key: HIVE-22068 > URL: https://issues.apache.org/jira/browse/HIVE-22068 > Project: Hive > Issue Type: Improvement > Reporter: Ashutosh Bapat > Assignee: Ashutosh Bapat > Priority: Major > Labels: pull-request-available > Attachments: HIVE-22068.01.patch, HIVE-22068.02.patch, > HIVE-22068.03.patch, HIVE-22068.04.patch, HIVE-22068.05.patch, > HIVE-22068.06.patch, HIVE-22068.07.patch > > Time Spent: 2h 20m > Remaining Estimate: 0h > > In repl load, update the status of target database to the last event dumped > so that repl status returns that and next incremental can specify it as the > event from which to start the dump. WIthout that repl status might return and > old event which might cause, older events to be dumped again and/or a > notification event missing error if the older events are cleaned by the > cleaner. > While at it > * Add more logging to DB notification listener cleaner thread > ** The time when it considered cleaning, the interval and time before which > events were cleared, the min and max id at that time > ** how many events were cleared > ** min and max id after the cleaning. > * In REPL::START document the starting event, end event if specified and the > maximum number of events, if specified. > * -- This message was sent by Atlassian Jira (v8.3.2#803003)