You were right regarding the closing bracket, however I am still not able to understand the working of the expert search:
when omitting the wrongly placed bracked and searching without the constraint that the "jahr" has to be a specific value then the result contains (among others)
{
"_index": "enaiored_0",
"_id": "0298256657124682BE68377B12A31455",
"_score": 5.331381,
"_source": {
"quote.quotenid": "Q00990",
"quote.quoteprozent": 15.5499,
"quote.anderemarken": [
"Sony Ericsson"
],
"quote.ungueltig": false,
"quote.herkunft": "IDC",
"quote.jahr": 2019.0,
"quote.von": "2021-03-26",
"id": "0298256657124682BE68377B12A31455",
"quote.marke": "Sony",
"quote.produkt": "Mobiltelefone"
}
},
Using the term "key_type:quote AND num_quote_jahr:2019.0" or "key_type:quote AND num_quote_jahr:2019" only yields
{
"took": 1,
"timed_out": false,
"hits": {
"max_score": "NaN",
"total": {
"value": 0,
"relation": "eq"
},
"hits": []
}
}
so no hits.
yes, for this specific example your standard query would suffice but what we want to achieve is a combination of this year request and the request as specified in
https://qa-rad.yuuvis.com/index.php?qa=1602&qa_1=expertmode-true-search-exact-string-matching-field resulting in ultimately one request with as few as possible results so the following calculations are not done on unnecessary "quoten".