FT.CREATE myindex SCHEMA post_title TEXT WEIGHT 5 SORTABLE post_name TEXT WEIGHT 1 post_content TEXT WEIGHT 1 post_type TEXT WEIGHT 1 SORTABLE post_excerpt TEXT WEIGHT 2 post_author TEXT WEIGHT 1 post_author_id NUMERIC post_id TEXT WEIGHT 1 SORTABLE menu_order NUMERIC SORTABLE post_status TEXT WEIGHT 1 SORTABLE post_date NUMERIC SORTABLE post_parent TEXT WEIGHT 1 SORTABLE search_index TEXT WEIGHT 1 taxonomy_category TAG SEPARATOR * taxonomy_id_category TAG SEPARATOR * taxonomy_post_tag TAG SEPARATOR * taxonomy_id_post_tag TAG SEPARATOR * taxonomy_nav_menu TAG SEPARATOR * taxonomy_id_nav_menu TAG SEPARATOR * taxonomy_link_category TAG SEPARATOR * taxonomy_id_link_category TAG SEPARATOR * taxonomy_post_format TAG SEPARATOR * taxonomy_id_post_format TAG SEPARATOR * taxonomy_language TAG SEPARATOR * taxonomy_id_language TAG SEPARATOR * taxonomy_post_translations TAG SEPARATOR * taxonomy_id_post_translations TAG SEPARATOR * taxonomy_term_language TAG SEPARATOR * taxonomy_id_term_language TAG SEPARATOR * taxonomy_term_translations TAG SEPARATOR * taxonomy_id_term_translations TAG SEPARATOR * taxonomy_target_group TAG SEPARATOR * taxonomy_id_target_group TAG SEPARATOR * taxonomy_topic TAG SEPARATOR * taxonomy_id_topic TAG SEPARATOR * taxonomy_forum TAG SEPARATOR * taxonomy_id_forum TAG SEPARATOR * taxonomy_qa_forum TAG SEPARATOR * taxonomy_id_qa_forum TAG SEPARATOR * taxonomy_location TAG SEPARATOR * taxonomy_id_location TAG SEPARATOR * taxonomy_media_category TAG SEPARATOR * taxonomy_id_media_category TAG SEPARATOR * active NUMERIC SORTABLE primary_topic TEXT WEIGHT 1 primary_target_group TEXT WEIGHT 1
``
We are running the official Docker image of version 1.6.2.
maanantai 23. syyskuuta 2019 9.29.28 UTC+2 Meir Shpilraien kirjoitti:
Try to run FT.EXPLAIN (or FT.EXPLAINCLI) on your query.
Ensure that the document was not modified outside of redisearch. Are you only using FT.ADD? or are you using FT.ADDHASH and then modifying the document
Can you try this with the 1.4 images? do you get the same results?
if the rdb is small enough, can you attach it to the issue?
Clearly seems like a bug. does it happen with other documents/queries too? are you using replace/update/delete operations?
is “test” an actual post type, or is it just a test entry. does it show up if you search for scheduled_chat_appointment without olla?
btw the latest tag is 1.6.3; not that I think it should affect your issue
I’d also suggest opening a ticket on github as it will make it easier for us to track,
Yeah, seems to happen with other documents and queries as well, and also other post_types. We are using replace operations but they don’t affect this problem, it appears even though no replace operations have been made. “Test” is an actual post type, just named test. And yeah, it shows up without the keyword as well. I can try updating to 1.6.3, but can’t do it right now as the deploy process means downtime which can’t be done during workday.
keskiviikko 25. syyskuuta 2019 9.43.04 UTC+2 Mark Nunberg kirjoitti:
We have over 10 000 quite big documents in the database so it’d be very difficult. I did just some tests on this in a separate environment indexing our content from scratch, and it didn’t affect the results. 1.6.1, 1.6.2 and 1.6.3 all have the same bug. I also ran 1.4.16 against the same database, and it returns the right results. So there clearly is a bug in 1.6.x on this.
keskiviikko 25. syyskuuta 2019 10.18.37 UTC+2 Meir Shpilraien kirjoitti: