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
[Feature Request] - Support More Common Type For Logging Currently Allegro Doesn'T Support Datetime

[Feature Request] - Support more common type for logging
Currently Allegro doesn't support datetime

ValueError: Only builtin types (str, int, str, float, list, tuple, dict, NoneType) are allowed for values (got data/train_start=>Timestamp, data/train_end=>Timestamp, data/valid_start=>datetime, data/valid_end=>datetime, data/test_start=>datetime, data/test_end=>datetime, data/val_start=>Timestamp, data/val_end=>Timestamp)

Posted 3 years ago
Votes Newest

Answers 4

EnviousStarfish54 which call are you using when you get this ValueError? connect_configuration() ?

Posted 3 years ago

SuccessfulKoala55 task.connect()

Posted 3 years ago

my workaround is making it into string before hand -> but it will breaks if I used trains-agent too since it will accept a string parameters instead of datetime

Posted 3 years ago

for workaround, I write a function to recursive cast my config dictionary into string if needed.

Posted 3 years ago
4 Answers
3 years ago
one year ago