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
Let'S Say That I Specify The

Let's say that I specify the output_uri parameter in Task.init like this:
task = Task.init( project_name="example_project", task_name="example_task", output_uri="/home/user/local_storage_path", )Why when I retrieve the output_uri path later via task.get_output_destination() it automatically prefixes it with file: , so that the absolute path becomes file:/home/user/local_storage_path ? This way the new path points to nowhere

  
  
Posted 2 years ago
Votes Newest

Answers 11


I currently deal with that by skipping the first 5 characters of the path, i. e. the 'file:' part. But I'm sure there is a cleaner way to proceed.

  
  
Posted 2 years ago

But this path actually does not exist in my system, so how should I fix that?

  
  
Posted 2 years ago

My idea is to take advantage of the capability of getting parameters connected to a task from another task to read the path where the artifacts are stored locally, so I don't have to define it again in each script corresponding to a different task.

  
  
Posted 2 years ago

I guess that was never the intention of the function, it just returns the internal representation. Actually my question would be, how do you use it, and why? :)

  
  
Posted 2 years ago

Sure, but I mean, apart from label it as a local path, what's the point of renaming the original path if my goal is to access it later using the name I gave it?

  
  
Posted 2 years ago

Now it's okey. I have found a more intuitive way to get around. I was facing the classic 'xy' problem :)

  
  
Posted 2 years ago

But you can get that directly, Task.get_task(...).artifacts[name].url , no? Am I missing something?

  
  
Posted 2 years ago

No, file://home/user/local_storage_path doesn't exist.

  
  
Posted 2 years ago

Hi GiganticTurtle0
you should actually get " file://home/user/local_storage_path "
With "file://" prefix.
We always store the file:// prefix to note that this is a local path

  
  
Posted 2 years ago

you mean "/home/user/local_storage_path" does not exist ?

  
  
Posted 2 years ago

But I'm sure there is a cleaner way to proceed.

Maybe ?!
path = task.get_output_destination().replace('file://', '', 1)

  
  
Posted 2 years ago
572 Views
11 Answers
2 years ago
one year ago
Tags