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 Everyone

Hi everyone 🙂 I Have a small question about the minio integration. I have launched the minio docker-compose, which is using the ~/clearml.conf file. After that I have installed a Minio instance locally with docker (for POC purpose) but I don't succeed to connect to minio, I have the "Missing key and secret for S3 storage access" error.
=> How can I know if the modification of the conf has been taken into account ?
=> Is there any CLI command which allow to check if the conf file is well formated ?
=> do you see any error with my conf :
{ # This will apply to all buckets in this host (unless key/value is specifically provided for a given bucket) host: "localhost:9000" key: "***************" secret: "****************" bucket: "clearml" multipart: false secure: false }Thanks !

  
  
Posted one year ago
Votes Newest

Answers 4


i guess it is... but still 😉

  
  
Posted one year ago

it's working thanks, it was due to 1) the Boto3 library which was not installed 2) the fact that I was working in a jupyter notebook & the clearML file was not reloaded (I think?)

  
  
Posted one year ago

thanks I am gonna check that.

PS : it's a toyset credential, thanks 🙂

  
  
Posted one year ago

Hey LuckyKangaroo60
So far there isnt a CLI command to check the conf file format : if there is an error, it is detected from the beginning of the execution and the program fails. Here is what i use as a conf for accessing my local docker based minio :

`
s3 {
# S3 credentials, used for read/write access by various SDK elements

        # Default, used for any bucket not specified below
        region: ""
        # Specify explicit keys
        key: "david"
        secret: "supersecret"
        # Or enable credentials chain to let Boto3 pick the right credentials. 
        # This includes picking credentials from environment variables, 
        # credential file and IAM role using metadata service. 
        # Refer to the latest Boto3 docs
        use_credentials_chain: false

        credentials: [
            # specifies key/secret credentials to use when handling s3 urls (read or write)
            # {
            #     bucket: "my-bucket-name"
            #     key: "my-access-key"
            #     secret: "my-secret-key"
            # },
            {
                 # This will apply to all buckets in this host (unless key/value is specifically provided for a given bucket)
                 host: "localhost:9000"
                 key: "david"
                 secret: "supersecret"
                 multipart: false
                 secure: false
             }
        ]
    } `ps. please blur your credentials  🙂
  
  
Posted one year ago
496 Views
4 Answers
one year ago
one year ago
Tags