You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hey all, i'm having a bit of trouble with retrieving results with hashtags for the OpenMeasures API. docs and interactive docs for reference. documentation seems to suggest that using a hashtag as is should work, but playing around with the query_type parameter + escaping the # symbol don't seem to work - getting results with the word but not the hashtag. GET and POST methods aren't allowed to see what's going on with the field mapping/analyzer so it looks like the # is getting stripped in some sort of tokenization process. OM leverages an Elasticsearch query_string_query which suggests this, but not sure if i can write over the analyzer via calls to the OM API with the given parameters. if not, i can just manually filter after the fact, but if there is some way to address this it would save time/api calls!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
hey all, i'm having a bit of trouble with retrieving results with hashtags for the OpenMeasures API. docs and interactive docs for reference. documentation seems to suggest that using a hashtag as is should work, but playing around with the query_type parameter + escaping the # symbol don't seem to work - getting results with the word but not the hashtag. GET and POST methods aren't allowed to see what's going on with the field mapping/analyzer so it looks like the # is getting stripped in some sort of tokenization process. OM leverages an Elasticsearch query_string_query which suggests this, but not sure if i can write over the analyzer via calls to the OM API with the given parameters. if not, i can just manually filter after the fact, but if there is some way to address this it would save time/api calls!
Beta Was this translation helpful? Give feedback.
All reactions