 |
 |
On 02/26/2015 04:14 PM, Serge Monkewitz wrote: > On Feb 26, 2015, at 12:39 PM, Daniel L. Wang <[log in to unmask]> wrote: > >> I would like to note that the current system requires the extra raObject and declObject columns in ForcedSource, so that table's size will be proportionally larger than it would be in production. > This is not quite true. The position of associated director table rows must be present in the CSV input to the partitioner. However, recall that the partitioner and data duplicator have the ability to drop columns while partitioning. Even if the data loader doesn’t quite support it yet, we should be able to produce something pretty close to the baseline ForcedSource schema (i.e. without object position or any of the other non-baseline columns that were produced by forced source measurement for stripe82). > ######################################################################## > 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 Ok, but launching SQL query against the secondary index to retrieve a source chunk w.r.t its objectId would avoid to run the partitioner against Source data? This might be faster and can also easily be map-reduced. Don't you think so? ######################################################################## 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