Description
Type
Metadata Access.
Behaviour
It provides enhanced searching on metadata.
Parameters
- container_filter: zero, one or more filters on containers’ names. Filters could be any type of search string accepted by SQL, with wildcards, OR-ed with pipes (filter1|filter2|...). Mute this filter with the default value “all”.
- metadata_key_filter: zero, one or more filters on metadata keys. Filters could be any type of search string accepted by SQL, with wildcards, OR-ed with pipes (filter1|filter2|...). Mute this filter with the default value “all”.
- metadata_value_filter: zero, one or more filters on metadata values. Filters could be any type of search string accepted by SQL, with wildcards, OR-ed with pipes (filter1|filter2|...). Mute this filter with the default value “all”.
- path: absolute/relative path used as the starting point of the recursive search. If not specified or in case of “-” (default), the recursive search will start at the cwd.
- cwd: absolute path corresponding to the current working directory, necessary to correctly parse paths. All resolved paths must be associated to the calling session, so they should contain “/<session-code>”.
- recursive : specifies if the search is done recursively or not. The argument is considered only for the first three levels and may have the following values:
- no : research only in current path (default)
- yes : research recursively starting from current path
System parameters
- exec_mode: operator execution mode. Possible values are async (default) for asynchronous mode, sync for synchronous mode with json-compliant output.
- ncores: number of parallel processes to be used (min. 1). This operator is not parallel, so the only possible value is 1.
- sessionid: session identifier used server-side to manage sessions and jobs. Usually, users don’t need to use/modify it, except when it is necessary to create a new session or switch to another one.
- objkey_filter: filter on the output of the operator written to file (default=all => no filter, none => no output, search => shows metadata list).
Examples
Get metadata with keys starting with “key” and values starting with “http” through a recursive search starting from “/absolute/path”:
[OPH_TERM] >> oph_search metadata_key_filter=key%;metadata_value_filter=http%;cwd=/absolute/path;
