[
https://issues.apache.org/jira/browse/GOBBLIN-1806?focusedWorklogId=856495&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-856495
]
ASF GitHub Bot logged work on GOBBLIN-1806:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Apr/23 16:32
Start Date: 12/Apr/23 16:32
Worklog Time Spent: 10m
Work Description: phet commented on PR #3667:
URL: https://github.com/apache/gobblin/pull/3667#issuecomment-1505582228
> Oh, I meant that I'll aggregate on the task level but let the client
handle aggregation on the dataset level, since it is rare to have a single
pipeline manage say tens of thousands of datasets.
yes, I agree, but think of it less ITO efficiency and how many ops when
performing aggregation, than of convenience: even if there are only 5, it still
requires a piece of code to total them per-event, within every downstream
analysis considering the job-level total. I believe this to be most analyses...
so although I generally recommend against de-normalized data structures, I
see the ready-to-use convenience out weighing the design principle. consider
the simple problem of counting by user, who's copying > 1TB in a job. it's
trivially simple to filter by bytes... but only so long with a job-level sum.
if the event has only task-level aggregation, the friction increases
considerably, whether in SQL or kusto.
Issue Time Tracking
-------------------
Worklog Id: (was: 856495)
Time Spent: 3h (was: 2h 50m)
> Create a GTE for recording bytes/records written for each dataset in a
> Gobblin job
> ----------------------------------------------------------------------------------
>
> Key: GOBBLIN-1806
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1806
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-core
> Reporter: William Lo
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Gobblin collects a lot of writer metrics on number of bytes and records
> written to the sinks, but does not emit these metrics as part of a
> GobblinTrackingEvent.
> We want to emit these in a GobblinTrackingEvent so that it can be ingested by
> montioring systems and GaaS.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
