Full table of contents#
- Introduction
- Administrator’s Guide
- User’s Guide
- Qserv SQL Dialect
- Introduction
- Selected Design Aspects
- Extensions
- Restrictions
- Spatial constraints should be expressed through our
qserv_areaspec_*
functions - Spatial constraints must appear at the beginning of
WHERE
- Only one spatial constraint is allowed per query
- Arguments passed to spatial constraints functions must be simple literals
OR
is not allowed afterqserv_areaspec_*
constraint- The director index constraint must be expressed through
=
,IN
, orBETWEEN
- Column(s) used in
ORDER BY
orGROUP BY
must appear inSELECT
- Expressions/functions in
ORDER BY
clauses are not allowed - Sub-queries are NOT supported
- Commands that modify tables are disallowed
- Outer joins are not supported with near-neighbor queries
- MySQL-specific syntax is not supported
- Repeated column names through
*
are not supported USE INDEX()
is not supported- Variables are not supported
- Spatial constraints should be expressed through our
- User Defined Functions
- Example Queries Supported
- Known Bugs
- Notes of Performance
- Asynchronous Query API
- HTTP frontend of Qserv
- Qserv SQL Dialect
- Ingesting catalogs
- Introduction
- The Ingest Workflow Developer’s Guide
- Introduction
- Main concepts
- Overview of the ingest workflow
- Plan the ingest
- Prepare the input data
- Register or un-publish a database
- Register tables
- Configure the Ingest service
- Start transactions
- Figure out locations of tables and chunks
- Send the data to the workers
- Monitor the progress of the ingest activities
- Commit/abort the transactions
- Publish the database
- Verify the ingested data products
- Perform the optional post-ingest data management operation on the ingested tables
- Types of tables in Qserv
- Transactions
- Table contributions
- Publishing databases and tables
- Database families
- Overview of the ingest workflow
- Simple Workflow Example
- Advanced Scenarios
- Global configuration options
- Character sets in contributions
- Concurrency control when processing async requests
- Ingesting tables into the published catalogs
- Transaction management
- Optimizations in using the REST services
- Options for making contribution requests
- Databases with many director tables
- Ingesting ref-match tables
- Using MySQL warnings for the data quality control
- Post-Ingest Data Management Tasks
- Ingest API Reference
- The Kubernetes-based Ingest Workflow
- Data preparation
- Developer’s Guide