Open DavidNelsonCordelia opened 4 years ago
any Updates on this issue ? @SwaySway @DavidNelsonCordelia
Any update on this would be much-appreciated @SwaySway @DavidNelsonCordelia
Sorry I have no update
There seems to be a bug, because in the generated schema.graphql file the multiMatch field has a String type:
input SearchableStringFilterInput {
ne: String
gt: String
lt: String
gte: String
lte: String
eq: String
match: String
matchPhrase: String
matchPhrasePrefix: String
multiMatch: String
exists: Boolean
wildcard: String
regexp: String
range: [String]
}
But according to Elastic docs it should be an object https://www.elastic.co/guide/en/elasticsearch/reference/6.2/query-dsl-multi-match-query.html
An answer or an explanation from the developer team would be highly appreciated.
This seems to be coming from 2019: https://github.com/aws-amplify/amplify-cli/issues/970 // already linked into description of this bug
It would be really nice to update documentation.
As best I can tell multiMatch does not work at all. Which is fine (I can do "or" queries to get the same result), but perhaps it should be removed from the docs?
Which Category is your question related to? graphQl
Amplify CLI Version 3.15
What AWS Services are you utilizing? dynamo, cognito, elastasearch s3
Provide additional details e.g. code snippets
I cannot get a multiMatch query to work. I have tried: const filterDescriptionBrand = {multiMatch:{query: searchString, fields: ["description", "brand", "category", "scanCode"]}};
and const filterDescriptionBrand = {multiMatch:{query: searchString, fields: "description brand category scanCode"}};
Both return values but no filtering occurs
Item aws-amplify/amplify-cli#970 also asks thios question but was closed with no answer