Page MenuHomePhabricator

[Epic] Migrate contribution tracking to new queue
Closed, DuplicatePublic


This might not be possible in our timeframe, but would be a huge win.

The only tricky design decision here is how to assign unique contribution tracking IDs. We could easily do something like UUID version 5, where each machine has its own sequence, and creates a UUID which includes its hostname as part of the hash input.

Anything that uses CTID (almost everything!) will have to know about the new UUID and use that as an index and identifier instead.

Event Timeline

Does this include finding a new wiki-side source for unique order IDs? Kafka doesn't seem to provide this.

Thanks! I'll add that to the description.

awight renamed this task from Migrate contribution tracking to new queue to [Epic] Migrate contribution tracking to new queue.Jul 15 2016, 2:06 AM
awight added a project: Epic.
awight updated the task description. (Show Details)
awight removed the point value for this task.