Information on resource '__system__/tap'
VESPA PA team server's Table Access Protocol (TAP) service with
table metadata.
Services defined within this resource descriptor
- VESPA PA team server TAP service
The VESPA PA team server's TAP end point. The Table Access
Protocol (TAP) lets you execute queries against our database tables,
inspect various metadata, and upload your own data. It is thus the
VO's premier way to access public data holdings.
Tables exposed through this endpoint include: epn_core from the gem_mars schema, epn_core from the nomad schema, epn_core from the soir schema, columns, groups, key_columns, keys, schemas, tables from the tap_schema schema.
Tables defined within this resource descriptor
- tap_schema.columns – queryable through TAP and ADQL
Columns in tables available for ADQL querying.
- tap_schema.groups – queryable through TAP and ADQL
Columns that are part of groups within tables available for ADQL
querying.
- tap_schema.key_columns – queryable through TAP and ADQL
Columns participating in foreign key relationships between tables
available for ADQL querying.
- tap_schema.keys – queryable through TAP and ADQL
Foreign key relationships between tables available for ADQL querying.
- tap_schema.schemas – queryable through TAP and ADQL
Schemas containing tables available for ADQL querying.
- tap_schema.supportedmodels
Standard data models supported by this service.
This is a non-standard tap_schema table used by DaCHS in the creation
of registry records. It is manipulated through gavo imp on tables with
supportsModel and supportsModelURI properties.
- tap_schema.tables – queryable through TAP and ADQL
Tables available for ADQL querying.
- tap_schema.tapjobs
A non-standard (and not tap-accessible) table used for managing
asynchronous TAP jobs. It is manipulated through TAP job creation and
destruction internally. Under very special circumstances, operators
can use the gavo admin cleantap command to purge jobs from this table.
Note that such jobs have corresponding directories in
$STATEDIR/uwsjobs, which will be orphaned if this table is manipulated
through SQL.
[Manage RD]