"Object"-like and "ForcedSource"-like table data downloaded and reformatted for MySQL ingest in December, partitioned for Qserv (~150,000 partitions)
Partitioning was on columns with the plain names "ra" and "dec" in both tables, and on the obvious foreign-key relationship between the tables. Referential integrity & consistency between the two spot-checked.
Overlap and data location will permit spatial joins between the Stripe 82 and WISE Object-like tables out to a 1 arcmin radius
Some discussion of whether the "substripe" scheme is optimal
Loading "Object"-like table into Qserv - tables loaded, now generating secondary indexes
Expecting to be able to test access through Qserv by the end of the day
Loading of "ForcedSource"-like tables awaits a restart of Qserv with updated containers (already built)
John Gates is working on improved handling / scheduling of Qserv queries with large result sizes
SUIT / IPAC
Trey Roby Early next week we will be ready to deploy our time-series viewer, assuming things work out with the cutout service
Questions about user table upload (e.g., to support bulk cone-search queries)
Fritz Mueller: Yes, there will be DAX support for this
For now, bulk queries will have to be done by iterating over single queries; should work at the level of 20 simultaneous queries being launched (c.f. underlying webserv 40-process pool)
Note that our new user is already interested in scales more like 10^3 to 10^5 objects in bulk queries.