If not, the data produced into Kafka may not be properly refineable into Hive.
We just encountered this for an hour of SearchSatisfaction data, and had to manually fix.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| eventlogging-processor - skip events for schemas migrated to Event Platform | operations/puppet | production | +32 -3 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Ottomata | T185233 Modern Event Platform | |||
| Open | Ottomata | T238230 Decommission EventLogging backend components by migrating to MEP | |||
| Declined | None | T259734 BUOD-KR1-Q4+: Certify that analytics schema and instruments have been upgraded to use the MEP system (clearing the legacy system for sunsetting) | |||
| Open | Ottomata | T259163 Migrate legacy metawiki schemas to Event Platform | |||
| Resolved | Ottomata | T262304 eventlogging-processor should fail to produce schemas that have been migrated to Event Platform |
Event Timeline
Comment Actions
- i think* this happens cause the clients are running an old version of the code prior to the changes, I wonder if all teh events are for domains we do not control
Comment Actions
Change 634314 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/puppet@production] eventlogging-processor - skip events for schemas that have been fully migrated to Event Platform
Comment Actions
Change 634314 merged by Ottomata:
[operations/puppet@production] eventlogging-processor - skip events for schemas migrated to Event Platform
Comment Actions
Mentioned in SAL (#wikimedia-analytics) [2020-10-19T14:40:02Z] <ottomata> restarted eventlogging-processor with filter to skip events already migrated to event platform - T262304