Open alexiv1965 opened 1 week ago
Does a bit another scenario has a difference? If you 1) create the table. 2) Alter it 3) insert the data 4) try your query ?
(that is - if you alter not AFTER data inserted, but BEFORE, so that insertion came to already altered table? Does it make a difference?)
Yep, I've reproduced your proposition, and results are exactly the same with my case:
id title brand score text_features 1372028895200542721 Crossbody Bag with Tassel Burberry 7031 {"bm25":732, "bm25a":0.65225315, "field_mask":2, "doc_word_count":1, "fields":[{"field":1, "lcs":1, "hit_count":2, "word_count":1, "tf_idf":0.51139158, "min_idf":0.25569579, "max_idf":0.25569579, "sum_idf":0.25569579, "min_hit_pos":1, "min_best_span_pos":1, "exact_hit":1, "max_window_hits":1, "min_gaps":0, "exact_order":1, "lccs":1, "wlccs":0.25569579, "atc":0.000000}], "words":[{"tf":2, "idf":0.25569579}]}
I.e. idf is from small global.idf, not altered large one. Only manticore restart helps.
Bug Description:
Continued from issue 1111:
I've two files: global.idf, very small, created as in reproduction steps, described in comments to issue 1111:
It produces:
Please, note "idf":0.25569579.
And now I want to change it to larger one, uploaded to s3: manticore/write-only/issue-2739/global_su.idf.gz:
The last line produces:
So, we can see that global_idf file has changed. But actually it is not loaded:
produces:
-- exactly the same idf value.
OK, let's restart manticore and repeat the last SELECT:
Now idf has correct value from new file global_su.idf.
Manticore Search Version:
commit 1611667, that fixes 1111
Operating System Version:
ubuntu 22.04
Have you tried the latest development version?
Yes
Internal Checklist:
To be completed by the assignee. Check off tasks that have been completed or are not applicable.