[
https://issues.apache.org/jira/browse/GOBBLIN-1933?focusedWorklogId=887663&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-887663
]
ASF GitHub Bot logged work on GOBBLIN-1933:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 27/Oct/23 23:55
Start Date: 27/Oct/23 23:55
Worklog Time Spent: 10m
Work Description: vikrambohra commented on code in PR #3806:
URL: https://github.com/apache/gobblin/pull/3806#discussion_r1375123656
##########
gobblin-completeness/src/main/java/org/apache/gobblin/completeness/verifier/KafkaAuditCountVerifier.java:
##########
@@ -171,16 +171,19 @@ private double calculateClassicCompleteness(String
datasetName, long beginInMill
for (String refTier: this.refTiers) {
Review Comment:
Trying to get more clarity here
Current Scenario:
source tier = gobblin, ref tier = agg cluster
What are the refTiers in the new scenario is it (agg cluster, local
cluster1) or (agg cluster, local cluster1,local cluster2,local cluster3 ) and
what is the expected behavior?
Issue Time Tracking
-------------------
Worklog Id: (was: 887663)
Time Spent: 0.5h (was: 20m)
> Change the logic in completeness verifier to support multi reference tier
> -------------------------------------------------------------------------
>
> Key: GOBBLIN-1933
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1933
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Zihan Li
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Change the logic in completeness verifier to support multi reference tier and
> use the lowest completeness percentage as the result.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)