| Table of Contents |
|---|
| outline | true |
|---|
Overview
This document captures the design of enhancements to data discovery in 4.0. Its main goal is to serve the Listing Center Home Page of CDAP 4.0.
...
The response would contain 2 fields, other than the above input parameters:
results- Contains a set of search results matching the search querytotal- specifies the total number of matched entities. This can be used to calculate the number of pages.
...
| Code Block |
|---|
$ curl http://localhost:11015/v3/namespaces/default/metadata/search?offset=50&size=2
{
"sort": "name asc,created_time desc",
"offset": 141,
"size": 10,
"total": 142,
"results": [
{
"entityId":{
"id":{
"applicationId":"PurchaseHistory",
"namespace":{
"id":"default"
}
},
"type":"application"
},
"metadata":{
"SYSTEM":{
"properties":{
"Flow:PurchaseFlow":"PurchaseFlow",
"MapReduce:PurchaseHistoryBuilder":"PurchaseHistoryBuilder"
},
"tags":[
"Purchase",
"PurchaseHistory"
]
}
}
},
{
"entityId":{
"id":{
"instanceId":"history",
"namespace":{
"id":"default"
}
},
"type":"datasetinstance"
},
"metadata":{
"SYSTEM":{
"properties":{
"type":"co.cask.cdap.examples.purchase.PurchaseHistoryStore"
},
"tags":[
"history",
"explore",
"batch"
]
}
}
}
]
} |
...
For 2 and 3, there could be an alternative to provide a UI-only (non-documented) batch endpoint.
Dataset Types in Metadata System
Currently, the Metadata System only supports artifacts, applications, programs, datasets, streams and stream views as entities. Is support for dataset types and modules necessary for 4.0?