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
Hi All! I Might Have Found An Issue With The Migration Guide.

Hi all!

I might have found an issue with the migration guide. None

We recently migrated our data to a new server.
While testing the migration, we found that all of our models had their MODEL URL set to the IP of the old server.

When migrating data that was saved to the local fileserver on 8081 , you apparently also need to rename all model URLs

Am i correct in assuming this? Should I submit an issue?

  
  
Posted one year ago
Votes Newest

Answers 5


That's OK, looks good!

  
  
Posted one year ago

is it possible to change an existing model's URL?

Edit the DBs ... That's basically the only way 😞

  
  
Posted one year ago

is it possible to change an existing model's URL?
would it be smart to try to do this straight on the database? Is it Mongodb?

  
  
Posted one year ago

good point about the hostname

  
  
Posted one year ago

Hi @<1556450111259676672:profile|PlainSeaurchin97>

While testing the migration, we found that all of our models had their

MODEL URL

set to the IP of the old server.

Yes all the artifacts/models/debug-samples are stored "as is" , this means that if you configured your original setup with IP, it is kind of stuck there, this is why it is always preferred to use host-name ...

you apparently also need to rename

all

model URLs

Yes 😞

  
  
Posted one year ago