Ophidia Logo

Ophidia

  • v1.4
    • v1.5
    • v1.4
    • v1.3
    • v1.2
  • Sections
      • Basics
      • Quick Start
      • User Guides
      • Administration Guides
      • Development Guides
  • « OPH_METADATA
  • OPH_SHOWGRID »
  •  Ophidia Website
  • Basics
  • Quick Start
  • User Guides
    • Terminal Usage
    • PyOphidia
    • Operators Manual
      • Data Analysis
      • Data Import/Export
      • Metadata
        • OPH_CONTAINERSCHEMA
        • OPH_CUBEELEMENTS
        • OPH_CUBEIO
        • OPH_CUBESCHEMA
        • OPH_CUBESIZE
        • OPH_METADATA
        • OPH_SEARCH
        • OPH_SHOWGRID
        • OPH_TASKS
      • Virtual File System
      • Workflow Management
      • Administration
      • Miscellaneous
    • Primitives Manual
    • Data model
    • Virtual File System
    • Massive Operations
    • Workflows Usage
    • Session Management
    • Time management
    • Examples
    • Appendix
  • Administration Guides
  • Development Guides

OPH_SEARCH¶

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>”.

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;

Arguments¶

Argument name Type Mandatory Values Default Min/Max-value
container_filter “string” “no”   “all”  
metadata_key_filter “string” “no”   “all”  
metadata_value_filter “string” “no”   “all”  
path “string” “no”   “-“  
cwd “string” “yes”      
exec_mode “string” “no” “async|sync” “async”  
sessionid “string” “no”   “null”  
ncores “int” “no”   “1” “1” / “1”
objkey_filter “string” “no” “all|none|search” “all”  

Ophidia project Ⓒ 2014-2019 CMCC Foundation. All Rights Reserved.

— Contact us — Privacy & Cookie —