![]() |
Page History
Excerpt | ||
---|---|---|
| ||
dm_query_dataobject |
If your user account has the Read , Write, or Own permission level on a collection or data file in DME, you can search you can search for that data. You can generate a list of such data files , with that match a search query. You can also specify a search path to narrow the search. The list provides the full path to each file in DME.
New collections and data files appear in search results 30-60 minutes after they were created.
To search for data:
- In your file local system, create a JSON file that specifies a search query. ( For more information, TBD)refer to Building a Query to Search for Data via the CLU.
Run the following command:
Panel borderColor silver borderStyle solid codeClipboard AllowLineWrap true dm_query_dataobject
[-D
REST-response]
[-o
output-file]
<criteria.json>
[search-path]
The following table describes each parameter:
Parameter Description [-D <REST-response>]
An optional parameter, specifying a path and filename in your file local system. The system always creates a response file:
- If you specify this parameter, the system saves the response from the server to the specified file in the specified location.
- If you omit this parameter, the system saves the file as query-dataobject-response-header.tmp in your home directory.
[-o <metadata<output-file>]
An optional parameter, specifying a path and filename in your file local system. The system always creates a metadata query output file:
- If you specify this parameter, the system saves the metadata query output to the specified file in the specified location.
- If you omit this parameter, the system prints the metadata query output to standard output and saves the file as query-dataobject-response-message.json.tmp in your home directory.
- .
<criteria.json>
A path and filename for a JSON file in your filelocal system, containing the compound query for the search. [search-path]
An optional parameter, specifying the path to the collection in DME in which you want to search.
For example, consider the following criteria.json file. When you perform a query, the system requires it in the context of a compoundQuery element with a join operator, even if it contains only one simple query.
Code Block |
---|
{
"compoundQuery": {
"operator": "AND",
"queries": [
{
"attribute": "source_file_size",
"value": "10",
"operator": "NUM_LESS_OR_EQUAL"
}
]
},
"detailedResponse": false,
"page": 1,
"totalCount": true
} |
With the above criteria.json file, the following command generates a list of data files in DME, in Project_1 and subcollections, that are size 10 or smaller. The output provides a total count of results and lists only the first page (the first 100 paths).
Panel | |||||
---|---|---|---|---|---|
| |||||
|
To generate the second page (the second 100 paths), set the page indicator to 2. To generate a list with metadata, set detailedResponse to true. Search for dataobjects based on the given compound query and optional search path.