You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've experienced problems when configuring WebAPI to use an MPP data warehouse (i.e. RedShift) to host the vocabulary since queries are generally queued if there is too much demand.
Instead, we'd propose a dedicated database that hosts the vocabularies you'd like to use in a PostgreSQL backend to configure with WebAPI. In addition, we may want to deprecate the 'vocabulary' daimon from v2.x of WebAPI in favor of this approach since a CDM should already have a vocabulary provided in the cdm schema.
The text was updated successfully, but these errors were encountered:
We've experienced problems when configuring WebAPI to use an MPP data warehouse (i.e. RedShift) to host the vocabulary since queries are generally queued if there is too much demand.
Instead, we'd propose a dedicated database that hosts the vocabularies you'd like to use in a PostgreSQL backend to configure with WebAPI. In addition, we may want to deprecate the 'vocabulary' daimon from v2.x of WebAPI in favor of this approach since a CDM should already have a vocabulary provided in the cdm schema.
The text was updated successfully, but these errors were encountered: