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
Answered
We'Re Getting Critical Alerts For Elasticsearch Container Around The Jdk Version. It'S Apparently End-Of-Life. Can You Look Into Upgrading The Image? It Looks Like You'Re Running Fixed Version (7.6.2) Instead Of Picking Up Either Latest Or Some Major/St

we're getting critical alerts for elasticsearch container around the JDK version. it's apparently end-of-life.

can you look into upgrading the image?

it looks like you're running fixed version (7.6.2) instead of picking up either latest or some major/stable version (if that is available on the docker repos)

or is there a new clearml server version I'm not aware of?

  
  
Posted 3 years ago
Votes Newest

Answers 14


hi SuccessfulKoala55 with the clearml server update, does it use a newer ES docker?

  
  
Posted 2 years ago

In fact I just did that yesterday. I'll let you know how it goes

  
  
Posted 3 years ago

Hi ElegantCoyote26 , not yet - we've been a little busy with the Free Hosted ClearML 🙂 Did you try using the latest ES docker in your own deployment meanwhile?

  
  
Posted 3 years ago

hi SuccessfulKoala55 ! has the docker compose been updated with this?>

  
  
Posted 3 years ago

If you see anything out of the ordinary - let us know 🙂

  
  
Posted 3 years ago

We're just now testing the latest ES docker, and it seems fine. I'll probably update the docker compose in the coming days. You can safely do it locally in your own docker-compose if you'd like

  
  
Posted 3 years ago

Hi SuccessfulKoala55 , do you have an update on this?

  
  
Posted 3 years ago

We'll take a look 🙂

  
  
Posted 3 years ago

any 7.6.2-x if I'm not wrong

  
  
Posted 3 years ago

Well, it's a possibility but I'd rather work with official images. What's the closest image that satisfied this condition?

  
  
Posted 3 years ago

"this means the elasticsearch feature set remains the same. and JDK versions are usually drop-in replacements when on the same feature level (ex. 1.13.0_2 can be replaced by 1.13.2)"

  
  
Posted 3 years ago

is this a possibility?

  
  
Posted 3 years ago

I understand! this is my sysadmin message:
"if nothing else, they could publish a new elasticsearch image of 7.6.2 (ex. 7.6.2-1) which uses a newer patched version of JDK (1.13.x but newer than 1.13.0_2)"

  
  
Posted 3 years ago

Hi ElegantCoyote26 ,
We're indeed planning to move to the newest version. It's always a delicate balance since sometimes upgraded versions require data migrations and/or code changes...

  
  
Posted 3 years ago
557 Views
14 Answers
3 years ago
one year ago
Tags