 |
 |
Serge and Daniel had a conversation on HipChat today about secondary indexes. It sounds like this is meant to handle indexes in addition to objectId that map from something to chunk number. I'm concerned because adding indexing on the czar adds another layer, another copy of data, more (shared) czar state, and another place for things to get out of sync and go wrong. Is there some way for us to lower the overhead of issuing queries to chunks so that we can just use "normal" local per-chunk indexes instead of a central index? -- Kian-Tat Lim, LSST Data Management, [log in to unmask] ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1