Project: datamanagement
Issue DM-510: Tweak metadata structure for driving table and secondary index
There seem to be confusion about driving table and secondary index. At the moment in zookeeper structure we have {code} /DATABASES//objIdIndex /DATABASES//TABLES//partitioning/secIndexColName /DATABASES//TABLES//partitioning/drivingTable /DATABASES//TABLES//partitioning/latColName /DATABASES//TABLES//partitioning/lonColName /DATABASES//TABLES//partitioning/keyColName {code} Issues to think about: * we can't call it objIdIndex, it is too lsst-specific. * drivingTable and keyColName - perhaps these should be at database level, which means we would only allow one drivingTable and one secondary index per database? * or, maybe instead of database level, it is a partitioning parameter? Note that two databases might use different name for secondary index or driving table, yet they might be joinable. That argues for introducing a new group, something like /DATABASE/partitioning in addition to /DATABASE_PARTITIONING. * consider renaming drivingTable to keyTable * do we really need secIndexColName and keyColName? Can't we get rid of one, and rename to keyColName?
Story points: 2