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")
Escape special characters +-&|!(){}[]^"~*?:\ - 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
 
Unanswered
← Adding data to vault on installation

Roy,

Great job discovering that install step! It's not often used, so it's possible we haven't seen it used by an external dev before on a local install and there's a bug. I'm guessing this is installed on your machine, either using WSL or a linux host since I don't see that path on the shared dev machine? With that information we can try to reproduce and patch it.

Brian

Posted 4 years ago
Brian Mego
45 × 1 Administrator
0

I got the error message while developing locally on a Linux machine.

— Roy Olav Purser   4 years ago
0

Great, will look into it. In the meanwhile, you can seed that data with the q2 vault CLI command. The caliper_admin script (which you probably ran to get set up) sets some environment variables. It should have set Q2SDK_VAULT_LOCAL_DIR=~/.vaultdir or something along those lines. When you type q2 vault add it should prompt you for some data, which will eventually go into that configured dir, simulating vault on your local filesystem.

— Brian Mego   4 years ago
38 Views
0 Answers
4 years ago
4 years ago