Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Unanswered
Hi, Our Server Ip Address Has Changed, And This Breaks All The Paths To Artifacts / Datasets. Is There A Way To Fix The Old Paths So That They Can Be Accessed Again? Thank You!


SucculentBeetle7 , this happens since the SDK uses the full URL of the registered image, when you use the fileserver but change its ip, you essentially break the links (this is why we recommend using a hostname, when possible). In order to change the urls to point to the new IP, you'll need to run a update_by_query API call against the ElasticSearch instance used by the server.

  
  
Posted 2 years ago
81 Views
0 Answers
2 years ago
one year ago