Describe the bug
When building search engines it's often important to ensure that indexing-time and query-time tokenization is performed in a similar or identical way.
If we don't do this, then the underlying tokens in the index may not be found at query-time.
During development it was discovered that this may not be occurring for knowledge graph queries.
To Reproduce
Steps to reproduce the behavior:
Run a knowledge-graph query against #25 for soymilk - curl -H 'Host: knowledge-graph' -XPOST 192.168.100.1:30080/ingredients/query --data 'descriptions[]=soymilk' | jq
Observe that no results are found:
{
"results": {
"soymilk": null
}
}
Expected behaviorsoy milk should be returned as a match, because it exists in the ingredient hierarchy and is a canonicalization of `soymilk.
Describe the bug When building search engines it's often important to ensure that indexing-time and query-time tokenization is performed in a similar or identical way.
If we don't do this, then the underlying tokens in the index may not be found at query-time.
During development it was discovered that this may not be occurring for knowledge graph queries.
To Reproduce Steps to reproduce the behavior:
soymilk-curl -H 'Host: knowledge-graph' -XPOST 192.168.100.1:30080/ingredients/query --data 'descriptions[]=soymilk' | jqExpected behavior
soy milkshould be returned as a match, because it exists in the ingredient hierarchy and is a canonicalization of `soymilk.