Me again,
seems it was a local problem for me.
The way Luiz mentioned is the exact correct way.
Thank you very much, Luiz
You helped me really out of this!
Am Montag, 7. April 2014 09:29:17 UTC+2 schrieb Alex K:
>
> Hello there,
>
> i have a query, example is this:
> {
> "query": {
>
Hi Luiz,
thank you again for your reply.
A colleague of mine told me that I might miss a plugin to use my
settings-file.
I will check this out and later write down here what I found out.
Sorry for all the trouble
Am Montag, 7. April 2014 09:29:17 UTC+2 schrieb Alex K:
>
> Hello there,
>
> i h
Hi Luiz,
thank you again for your reply.
I don't fully understand the part you mentioned:
After index one document with the title equals do "core":
>
> curl -XPOST 'localhost:9200/myindex/test/1' -d '{
> "title": "core"
> }'
>
Sorry, I am pretty new to ES and haven't understand pretty much.
Hi Alex,
First create your index with the synonym filter:
curl -XPUT 'localhost:9200/myindex/' -d '{
"settings": {
"index": {
"analysis": {
"filter": {
"synonym_filter": {
"type": "synonym",
Hello Luiz, thank you for your reply!
As we use rivers, I was told to declare the analyzer there.
It looks like this for me:
{
"index" : {
"analysis" : {
"filter" : {
"synonym_filter" : {
"type" : "synonym",
"synonyms" : [
Hi Alex,
If the fields you are searching ("TITLE","SHORTDESC") were indexed using an
analyzer that declares synonyms the "multi_match" query will use it. It
happens because the multi_match query use the analyzer explicit defined in
mapping or the default analyzer.[1]
You can explicit declare the
Hello there,
i have a query, example is this:
{
"query": {
"bool": {
"should": [
{
"multi_match": {
"query": "foo",
"fields": [
"TITLE",