Open lmarini opened 2 years ago
Spent some time on this, issue I believe is with the dashed term being split into multiple tokens in ES (it treats the - as a stop character) resulting in weird behavior on search evaluation. I was able to find the dataset using "Dashes", for example, but not "Test-Dashes" or "Test Dashes".
Tried changing default tokenizer to whitespace tokenizer and a couple other tokenizers suggested by ES, but they were not returning results as I expected. The only other idea I had was to change the query we build (from "query_string" to something else) but that will likely have ripple effects on the behavior of other cases we've encountered in the past and possibly cause other things to break so I am hesitant.
When creating a resource with a dash in the name (a dataset for example), search doesn't find the resource, even though a query directly against elasticsearch will find it. The assumption is Clowder is escaping dashes in such a way that it can't match it. Underscores work instead and are work around.
To Reproduce Steps to reproduce the behavior:
Clowder v1.20.2