 |
 |
Folks, > Here's what's happening: > qserv_areaspec_box asks qserv to choose chunk/row coverage according > to the director table. Generally, it detects the director table from > the query, computes the region against the index, and then > substitutes the right directive. But in this case, there is no > director table, only a child table. Hence, even if we know what the > director table is, its columns are not available to use in the > query, unless we rewrite to add an equi-join with the director > table. The best we can do in this case (without adding a join), is > to use the parameters for determining chunk coverage, and then > covering all rows in those chunks. The user could specify additional > conditions to apply spatial filtering based on other > (non-partitioning) columns. I agree; if qserv_areaspec_box is specified to work only against Object (or other director table) ra/decl columns, then using it in a query where those columns are unavailable should be rejected. I think auto-including the director table with a join is more magic than is needed. ForcedSources don't contain ra/decl (or even x,y), so specifying a box for them is inappropriate. -- 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