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! Is There A Way To Rename The Default "Args" Name For Task Configuration That Is Being Automatically Created When The Code Contains Argparse?

Hi all!
Is there a way to rename the default "Args" name for task configuration that is being automatically created when the code contains argparse?

  
  
Posted 10 months ago
Votes Newest

Answers 3


Hi @<1523701070390366208:profile|CostlyOstrich36> , thanks for the response!
I want to implement the user arguments for the task using argparse, but I want to change the default "Args" name to a name that I will set

  
  
Posted 10 months ago

Why is it not possible to use argparse and then when I do:
Task.init() I add:

auto_connect_arg_parser=False

and then I read the arguments to dict and use task.connect(arg_dict, name=my_custom_name)?

I tried doing that but it doesn't work when I clone a task from the UI (meaning it will not work in pipeline as well)

  
  
Posted 10 months ago

Hi @<1539417873305309184:profile|DangerousMole43> , I'm afraid this is not configurable currently. What is your use case?

  
  
Posted 10 months ago
652 Views
3 Answers
10 months ago
10 months ago
Tags