2ce025a906
Fixes after rebase to fix new issues.
2022-10-25 20:58:31 +02:00
6b2fe94192
Fixes for clippy bringing us down to 18 remaining issues.
...
This brings us a step closer to enforcing clippy on each build.
2022-10-25 20:49:02 +02:00
be302fd250
Remove outdated workaround for duplicate words in phrase search
2022-10-24 15:27:06 +02:00
a983129613
Apply suggestions from code review
2022-10-20 09:49:37 +02:00
e6e76fbefe
Improve performance of resolve_phrase at the cost of some relevancy
2022-10-18 10:37:34 +02:00
830a7c0c7a
Use resolve_phrase function for exactness criteria as well
2022-10-18 10:37:34 +02:00
18d578dfc4
Adjust some algorithms using DBs of word pair proximities
2022-10-18 10:37:34 +02:00
1dbbd8694f
Rename StrStrU8Codec to U8StrStrCodec and reorder its fields
2022-10-18 10:37:34 +02:00
81919a35a2
Update milli/src/search/criteria/initial.rs
...
Co-authored-by: Clément Renault <clement@meilisearch.com >
2022-10-17 18:23:20 +02:00
516e838eb4
Update milli/src/search/criteria/initial.rs
...
Co-authored-by: Clément Renault <clement@meilisearch.com >
2022-10-17 18:23:15 +02:00
6f55e7844c
Add some code comments
2022-10-17 14:41:57 +02:00
cf203b7fde
Take filter in account when computing the pages candidates
2022-10-17 14:13:44 +02:00
d71bc1e69f
Compute an exact count when using distinct
2022-10-17 14:13:44 +02:00
a396806343
Add settings to force milli to exhaustively compute the total number of hits
2022-10-17 14:13:44 +02:00
e4a52e6e45
Merge #594
...
594: Fix(Search): Fix phrase search candidates computation r=Kerollmops a=ManyTheFish
This bug is an old bug but was hidden by the proximity criterion,
Phrase searches were always returning an empty candidates list when the proximity criterion is deactivated.
Before the fix, we were trying to find any words[n] near words[n]
instead of finding any words[n] near words[n+1], for example:
for a phrase search '"Hello world"' we were searching for "hello" near "hello" first, instead of "hello" near "world".
Co-authored-by: ManyTheFish <many@meilisearch.com >
2022-08-17 13:22:52 +00:00
8c3f1a9c39
Remove useless lifetime declaration
2022-08-17 15:20:43 +02:00
748bb86b5b
cargo fmt
2022-08-10 15:53:46 +02:00
d2e01528a6
Switch to snapshot tests for search/criteria/typo.rs
2022-08-10 15:53:46 +02:00
a9c7d82693
Switch to snapshot tests for search/criteria/attribute.rs
2022-08-10 15:53:46 +02:00
b389be48a0
Factorize phrase computation
2022-08-08 10:37:31 +02:00
cbb3b25459
Fix(Search): Fix phrase search candidates computation
...
This bug is an old bug but was hidden by the proximity criterion,
Phrase search were always returning an empty candidates list.
Before the fix, we were trying to find any words[n] near words[n]
instead of finding any words[n] near words[n+1], for example:
for a phrase search '"Hello world"' we were searching for "hello" near "hello" first, instead of "hello" near "world".
2022-07-21 10:04:30 +02:00
6b2c2509b2
fix bug in exact search
2022-04-04 20:54:03 +02:00
56b4f5dce2
add exact prefix to query_docids
2022-04-04 20:54:03 +02:00
21ae4143b1
add exact_word_prefix to Context
2022-04-04 20:54:03 +02:00
c4c6e35352
query exact_word_docids in resolve_query_tree
2022-04-04 20:54:02 +02:00
49d59d88c2
Remove useless variables in proximity
2022-03-16 16:12:52 +01:00
21ec334dcc
Fix the compilation error of the dependency versions
2022-03-15 11:17:45 +01:00
13de251047
rewrite word pair distance gathering
2022-02-03 15:57:20 +01:00
d852dc0d2b
fix phrase search
2022-02-01 20:21:33 +01:00
98a365aaae
store the geopoint in three dimensions
2021-12-14 12:21:24 +01:00
360c5ff3df
Remove limit of 1000 position per attribute
...
Instead of using an arbitrary limit we encode the absolute position in a u32
using one strong u16 for the field id and a weak u16 for the relative position in the attribute.
2021-10-12 10:10:50 +02:00
085bc6440c
Apply PR comments
2021-10-06 11:12:26 +02:00
1bd15d849b
Reduce candidates threshold
2021-10-05 18:52:14 +02:00
ea4bd29d14
Apply PR comments
2021-10-05 17:35:07 +02:00
3296bb243c
Simplify word level position DB into a word position DB
2021-10-05 12:15:02 +02:00
75d341d928
Re-implement set based algorithm for attribute criterion
2021-10-05 12:14:50 +02:00
2e49230ca2
Update milli/src/search/criteria/attribute.rs
...
Co-authored-by: Clément Renault <clement@meilisearch.com >
2021-09-29 14:49:45 +02:00
7ad0214089
Update milli/src/search/criteria/attribute.rs
...
Co-authored-by: Clément Renault <clement@meilisearch.com >
2021-09-29 14:49:41 +02:00
1df5b8712b
Hotfix meilisearch#1707
2021-09-29 14:41:56 +02:00
257e621d40
create an asc_desc module
2021-09-22 16:37:41 +02:00
c695a1ffd2
add the possibility to sort by descending order on geoPoint
2021-09-15 11:49:58 +02:00
91ce4d1721
Stop iterating through the whole list of points
...
We stop when there is no possible candidates left
2021-09-15 11:49:58 +02:00
3fc145c254
if we have no rtree we return all other provided documents
2021-09-09 17:44:09 +02:00
a84f3a8b31
Apply suggestions from code review
...
Co-authored-by: Clément Renault <clement@meilisearch.com >
2021-09-09 15:09:35 +02:00
b15c77ebc4
return an error in case a user try to sort with :desc
2021-09-08 18:24:09 +02:00
4f69b190bc
remove the distance from the search, the computation of the distance will be made on meilisearch side
2021-09-08 18:24:09 +02:00
b1bf7d4f40
reformat
2021-09-08 18:24:09 +02:00
aca707413c
remove the memory leak
2021-09-08 18:24:09 +02:00
a8a1f5bd55
move the geosearch criteria out of asc_desc.rs
2021-09-08 18:24:09 +02:00
13c78e5aa2
Implement the _geoPoint in the sortable
2021-09-08 18:24:09 +02:00
