Closed ivankristianto closed 6 years ago
The post with title "Image Alignment" should not appear in search result because it doesn't have any keyword inside the content/title.
Found the weird result:
"description": "weight(post_content:job in 11) [PerFieldSimilarity], result of:",
it look for keyword "job" instead of "Rob Dyrdek"
That's a fuzzy match. Check out the fuzziness parameter. Those matches should be weighted less than exact matches.
Yeah, still find out how to weight it less then the exact match. Even the boost is 4 for the exact match.
I got some light about this irrelevant result. It is because of the decay functions:
"exp": {
"post_date_gmt": {
"scale": "14d",
"decay": 0.05,
"offset": "7d"
}
}
The old post score will reduce a lot, even it has the exact match. So I wonder if this how it should be or should be fixed?
Can you take an export of these posts so I can test on my local?
My setup is pretty easy:
And try to search
@ivankristianto can you confirm the fix for this?
Yes, it does fix the relevance issue.
I think We need an option to enable/disable this decay functions for certain post type. for example: article like knowledge based might work for a long time. So this decay function will make it less relevance.
What do you think @tlovett1 ?
Let's punt discussion to 2.3.
We just launched a new site using latest WP version, ES 5.2.2 and EP plugin version 2.2.1. Unfortunately, many of the results are not relevant. We have ~101,000 docs spread over 5 shards.
Here's an example query:
As you can see the first two results do not contain the string "lacrosse". The second two do, but many afterwards also do not contain that string or anything close to "lacrosse" I don't believe.
Could someone please take a look at the following results from the Debug EP plugin and let me know if you seen anything that might be causing this issue and if there's a way to adjust any of the parameters to improve relevancy. We are NOT using a custom wp_query but we are using a custom search results template and are using a "q" query parameter rather than the "s" parameter. I'm wondering if this set up might be conflicting with EP.
Debug results: https://www.dropbox.com/s/znyoj5fd2v08sha/elasticpress-debug-results.txt?dl=0
Thanks so much for any help you can provide!
Steve
Well, right after I wrote the previous comment, I upgraded to EP 2.3 and that appears to have mostly fixed, or entirely fixed the issue. I had waited to upgrade because I did not see any mention of a fix in the release notes, but perhaps I just missed it. Anyhow, there may not be an issue now. If you have any other insight as to why 2.3 would have fixed this issue, please let me know. :-)
@sjferwerda not sure what cause the fixed on your end. Did you do reindexing after the upgrade? If yes, that might have fixed it.
Nope, did not re-index on our end. I guess it's not an issue now. Thanks for your help!
Closing.
I'm using: WP: 4.7.2 EP: 2.2 ES: 5.0.0 Content from theme-unit-test-data.xml
wp elasticpress stats
resultKeyword: "Rob Dyrdek"
POST Query:
Results
related to issue #699