2f9f6a1f21
Merge #169
...
169: Optimize roaring codec r=Kerollmops a=MarinPostma
Optimize the `BoRoaringBitmapCodec` by preventing it from emiting useless error that caused allocation. On my flamegraph, the byte_decode function went from 4.13% to 1.70% (of transplant graph).
This may not be the greatest optimization ever, but hey, this was a low hanging fruit.
before:

after:

Co-authored-by: Marin Postma <postma.marin@protonmail.com >
2021-06-01 06:30:25 +00:00
984dc7c1ed
rewrite roaring codec without byteorder.
2021-05-31 22:15:39 +02:00
1373637da1
optimize roaring codec
2021-05-31 22:15:35 +02:00
6609f9e3be
review edits
2021-05-31 18:41:37 +02:00
1df68d342a
Make the MatchingWords return the number of matching bytes
2021-05-31 18:22:29 +02:00
b8e6db0feb
Add database in infos crate
2021-05-31 16:29:27 +02:00
c701f8bf36
Use field id word count database in exactness criterion
2021-05-31 16:27:28 +02:00
4ddf008be2
add field id word count database
2021-05-31 16:27:28 +02:00
1c4f0b2ccf
clippy, fmt & tests
2021-05-31 16:03:39 +02:00
10fc870684
improve dump info reports
2021-05-31 15:49:04 +02:00
2f5e61bacb
Merge #184
...
184: Transfer numbers and strings facets into the appropriate facet databases r=Kerollmops a=Kerollmops
This pull request is related to https://github.com/meilisearch/milli/issues/152 and changes the layout of the facets values, numbers and strings are now in dedicated databases and the user no more needs to define the type of the fields. No more conversion between the two types is done, numbers (floats and integers converted to f64) go to the facet float database and strings go to the strings facet database.
There is one related issue that I found regarding CSVs, the values in a CSV are always considered to be strings, [meilisearch/specifications#28 ](d916b57d74/text/0028-indexing-csv.md
) fixes this issue by allowing the user to define the fields types using `:` in the "CSV Formatting Rules" section.
All previous tests on facets have been modified to pass again and I have also done hand-driven tests with the 115m songs dataset. Everything seems to be good!
Fixes #192 .
Co-authored-by: Clément Renault <clement@meilisearch.com >
Co-authored-by: Kerollmops <clement@meilisearch.com >
2021-05-31 13:32:58 +00:00
1c0a5cd136
Resolve code modification suggestions
2021-05-31 15:22:50 +02:00
dffbaca63b
bump sentry version
2021-05-31 13:59:31 +02:00
b3c8f0e1f6
fix empty index error
2021-05-31 10:58:51 +02:00
bc5a5e37ea
fix dump v1
2021-05-31 10:42:31 +02:00
33c6c4f0ee
add timestamos to dump info
2021-05-30 15:55:17 +02:00
39c16c0fe4
fix dump import
2021-05-30 12:35:17 +02:00
1cb64caae4
dump content is now only uuid
2021-05-29 00:08:17 +02:00
b258f4f394
fix dump import
2021-05-27 14:30:20 +02:00
c47369839b
dump meta
2021-05-27 10:51:19 +02:00
b924e897f1
load index dump
2021-05-27 10:27:47 +02:00
e818c33fec
implement load uuid_resolver
2021-05-26 20:42:09 +02:00
76b9178b16
Merge #200
...
200: Fix plane sweep algorithm r=Kerollmops a=LegendreM
Fix plain sweep algorithm after creating some tests on proximity.
Co-authored-by: many <maxime@meilisearch.com >
2021-05-26 11:36:24 +00:00
a5e98cf46d
Fix plane sweep algorithm
2021-05-25 18:21:55 +02:00
9278a6fe59
integrate in dump actor
2021-05-25 18:14:11 +02:00
3593ebb8aa
dump updates
2021-05-25 16:44:58 +02:00
464639aa0f
udpate actor error improvements
2021-05-25 16:44:58 +02:00
4acbe8e473
implement index dump
2021-05-25 16:44:58 +02:00
7ad553670f
index error handling
2021-05-25 16:44:58 +02:00
2185fb8367
dump uuid resolver
2021-05-25 16:44:54 +02:00
cbcf50960f
Merge pull request #192 from meilisearch/dumps-tasks
...
Dumps tasks
2021-05-25 15:49:15 +02:00
89846d1656
improve panic message
2021-05-25 15:47:57 +02:00
e5175f5dc1
merge
2021-05-25 15:24:39 +02:00
1a6dcec83a
crash when the actor have no inbox
2021-05-25 15:23:13 +02:00
fe260f1330
Update meilisearch-http/src/index_controller/dump_actor/actor.rs
...
Co-authored-by: marin <postma.marin@protonmail.com >
2021-05-25 15:13:47 +02:00
5012cc3a32
Fix the http-ui crate to support split facet databases
2021-05-25 11:31:06 +02:00
28bd9e183e
Fix the infos crate to support split facet databases
2021-05-25 11:31:06 +02:00
3a4a150ef0
Fix the tests and remaining warnings
2021-05-25 11:31:06 +02:00
02c655ff1a
Refine the facet distribution to use both databases
2021-05-25 11:30:00 +02:00
79efded841
Refine the FacetCondition from_array constructor
2021-05-25 11:30:00 +02:00
f7efde11d9
Refine the facet condition to use both facet databases
2021-05-25 11:30:00 +02:00
e62b89a2ed
Make the facet distinct work with the new split facets
2021-05-25 11:30:00 +02:00
bd7b285bae
Split the update side to use the number and the strings facet databases
2021-05-25 11:30:00 +02:00
038e03a4e4
Use both facet databases in the FacetIter type
2021-05-25 11:30:00 +02:00
597144b0b9
Use both number and string facet databases in the distinct system
2021-05-25 11:29:59 +02:00
837c1041c7
Clear and delete the documents from the facet database
2021-05-25 11:28:36 +02:00
a56c46b6f1
Explode the string and f64 facet databases into two
2021-05-25 11:28:36 +02:00
df7a32e3d0
Move the creation date initialization into a function
2021-05-25 11:28:35 +02:00
991d8e1ec6
fix the error printing
2021-05-25 10:48:57 +02:00
49a0e8aa19
use a RwLock instead of a Mutex
2021-05-24 18:19:34 +02:00