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
This endpoint should return a schema as to how an end user can define their own manual metadata filters. Without this endpoint, neither an end user nor a third-party applications, e.g., RAIL, can have an idea of what metadata fields and their respective constraints are applied to a specific asset type.
For instance as an example, Dataset asset type may support the metadata filtering on the following fields with individually specified value constraints. The goal of this endpoint is to clearly and precisely define what these fields are:
task_type: can only be a value from a list of 30 predefined task types
languages: can only be a string of size 2
size_in_mb: only non-negative values, float type in a range of [0, 1e+9]
The text was updated successfully, but these errors were encountered:
This endpoint should return a schema as to how an end user can define their own manual metadata filters. Without this endpoint, neither an end user nor a third-party applications, e.g., RAIL, can have an idea of what metadata fields and their respective constraints are applied to a specific asset type.
For instance as an example,
Dataset
asset type may support the metadata filtering on the following fields with individually specified value constraints. The goal of this endpoint is to clearly and precisely define what these fields are:task_type
: can only be a value from a list of 30 predefined task typeslanguages
: can only be a string of size 2size_in_mb
: only non-negative values, float type in a range of [0, 1e+9]The text was updated successfully, but these errors were encountered: