Page MenuHomePhabricator

Investigate / Correct timestamp and data not being properly read from Camus for CirrusSearchRequestSet logs.
Closed, ResolvedPublic

Description

Data imported with kafka seems not to have the data timsestamp, but the import-time timestamp.

Event Timeline

JAllemandou raised the priority of this task from to Needs Triage.
JAllemandou updated the task description. (Show Details)
JAllemandou added a project: Analytics-Kanban.
JAllemandou subscribed.

Change 251267 had a related patch set uploaded (by DCausse):
AvroBinaryMessageDecoder: added "ts" as a possible record for timestamp

https://gerrit.wikimedia.org/r/251267

JAllemandou set Security to None.
JAllemandou moved this task from Next Up to In Code Review on the Analytics-Kanban board.

Change 252432 had a related patch set uploaded (by DCausse):
Rename timestamp to ts for CirrusSearchRequestSet

https://gerrit.wikimedia.org/r/252432

Nuria renamed this task from Investigate / Correct timestamp not being properly read from Camus for CirrusSearchRequestSet logs. to Investigate / Correct timestamp and data not being properly read from Camus for CirrusSearchRequestSet logs..Nov 20 2015, 5:04 PM
Nuria subscribed.

Change 251267 merged by jenkins-bot:
Add support for custom timestamp and schema rev id in avro message decoders

https://gerrit.wikimedia.org/r/251267

Change 252432 merged by Ottomata:
Rename timestamp to ts for CirrusSearchRequestSet

https://gerrit.wikimedia.org/r/252432