...
The BusinessMetadataDataset dataset type introduced in 3.2 will be renamed to MetadataDataset, since it will also serve system metadata in 3.3. For existing CDAP installations, we will need an upgrade step to change the type of the existing "business.metadata" dataset in the "datasets.instance" table.
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
REST APIs
- The Metadata REST APIs to retrieve properties and tags will be updated to accept a scope query parameter. It will support the values user and system. If scope is not specified, the API will return all metadata across both scopes.
- New APIs will be added for View and artifacts:
Purpose | API | Body | Response | Routable | Comments | Approved? | ||
---|---|---|---|---|---|---|---|---|
Annotate business metadata for view | POST /v3/namespaces/{namespace-id}/streams/{stream-id}/views/{view-id}/metadata/properties |
| 200: Successful 404: view not found in specified namespace | Yes |
|
| ||
Retrieve business metadata for view | GET /v3/namespaces/{namespace-id}/stream/{stream-id}/views/{view-id}/metadata/properties | N/A | 200: Successful 404: View not found in specified namespace
| Yes | ||||
Delete all business metadata for view | DELETE /v3/namespaces/{namespace-id}/streams/{stream-id}/views/{view-id}/metadata/properties |
| 200: Successful 404: View not found in specified namespace | Yes | ||||
Delete selected key from business metadata for view | DELETE /v3/namespaces/{namespace-id}/streams/{stream-id}/views/{view-id}/metadata/properties/{key} |
| 200: Successful 404: View not found in specified namespace | Yes | ||||
Search views containing business metadata | GET /v3/namespaces/{namespace-id}/metadata/search?query=term&target=view | N/A | 200: Successful
| Yes |
| |||
Add tags to a view | POST /v3/namespaces/{namespace-id}/streams/{stream-id}/views/{view-id}/metadata/tags |
| 200: Successful 404: View not found in specified namespace | Yes |
|
| ||
Retrieve view tags | GET /v3/namespaces/{namespace-id}/streams/{stream-id}/views/{view-id}/metadata/tags | N/A |
| Yes | ||||
Remove all view tags | DELETE /v3/namespaces/{namespace-id}/streams/{stream-id}/views/{view-id}/metadata/tags |
| 200: Successful 404: View not found in specified namespace | Yes | ||||
Remove specified view tag | DELETE /v3/namespaces/{namespace-id}/streams/{stream-id}/views/{view-id}/metadata/tags/{tag} |
| 200: Successful 404: View not found in specified namespace | Yes | ||||
Get all business metadata for a view | GET /v3/namespaces/{namespace-id}/streams/{stream-id}/views/{view-id}/metadata |
| 200: Successful 404: View not found in specified namespace | Yes | Retrieves all properties and tags for a stream. |
Questions
- The REST APIs to retrieve metadata will accept an additional scope parameter. Is it considered a backward incompatible change that if the scope is not specified, the API will now return all metadata, and not just business metadata, like it did in 3.3?
...