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, I’Ve Set Up A Clearml Server With The Default_Output_Uri Pointed To S3. We’Re Planning To Migrate From S3 To Azure Blob Storage. Is There A Direct Way To Migrate The Data, Or Should We Simply Transfer The Data From S3 To Azure And Update The Default_

Hi,
I’ve set up a ClearML server with the default_output_uri pointed to S3. We’re planning to migrate from S3 to Azure Blob Storage.

Is there a direct way to migrate the data, or should we simply transfer the data from S3 to Azure and update the default_output_uri to the new Azure Blob Storage path?

Thanks in advance

  
  
Posted 4 months ago
Votes Newest

Answers 4


Hi @<1523701087100473344:profile|SuccessfulKoala55> ,
We have successfully created a sample for the migration. Here are the changes:

  • URL for MongoDB from s3:// to azure://
  • Elasticsearch as you suggested
    However, our main focus is that most of our production fetches models from ClearML, which are configured with s3:// URLs.

There is an issue/bug in the UI when downloading via Azure. Here are the details: None .

  
  
Posted 4 months ago

Hi @<1523701260895653888:profile|QuaintJellyfish58> , see here for an example on how to accomplish that: None

  
  
Posted 4 months ago

Thanks guys, i will try to learn that first. i will updates when executing these ideas. @<1523701087100473344:profile|SuccessfulKoala55> @<1590514584836378624:profile|AmiableSeaturtle81> 🙌

  
  
Posted 4 months ago

We had a similar problem. Clearml doesnt support data migration (not that I know of)
So you have two ways to fix this:

  • Recreate the dataset when its already in Azure
  • Edit each elasticsearch database file entry to point to new destination (we did this)
  
  
Posted 4 months ago
555 Views
4 Answers
4 months ago
4 months ago
Tags
Similar posts