3 ms·
(former Uber engineer) Data lived in many databases across the company. Vertica, hive, schemaless, Cassandra, etc. The value in a column might refer to an id i
by bastawhiz 9y ago
(former Uber engineer)
Data lived in many databases across the company. Vertica, hive, schemaless, Cassandra, etc. The value in a column might refer to an id in an entirely different system. When you have (tens of?) thousands of tables owned by hundreds of teams, documentation is neither homogeneous nor centralized.
- jmiserez 9y agoI see. Very cool approach to have a tool replace people reading documentation, and certainly more accurate and up-to-date. Also I re-read only now that this is for a DWH, in which case it makes even more sense.
- fusiongyro 9y agoSo, why does it make sense in this situation ("you can all do what you please with your data") to mandate something technical ("but starting today you all must use UUIDs from now on") across all groups? What's the value of this change if using UUIDs is now literally the only thing they all have in common?
- jhoechtl 9y agoProcess mining to identify yet unknown relationships. This is more sort of a big data "what relates to each-other yet we don't know it" analysis
- dllthomas 9y agoThe change to UUIDs was part of a larger effort to make sure everything that generated entities could do it without synchronization across datacenters. (And sure, there are other approaches, I'm just adding some context :) )