Commit Graph

998 Commits

Author SHA1 Message Date
0efa011e09 Make a small code clean-up 2021-04-27 14:39:52 +02:00
17c8c6f945 Make set algorithm return None when nothing can be returned 2021-04-27 14:39:52 +02:00
b3e2280bb9 Debug attribute criterion
* debug folding when initializing iterators
2021-04-27 14:39:52 +02:00
1eee0029a8 Make attribute criterion typo/prefix tolerant 2021-04-27 14:39:52 +02:00
59f58c15f7 Implement attribute criterion
* Implement WordLevelIterator
* Implement QueryLevelIterator
* Implement set algorithm based on iterators

Not tested + Some TODO to fix
2021-04-27 14:39:52 +02:00
361193099f Reduce the amount of branches when query tree flattened 2021-04-27 14:39:52 +02:00
e65bad16cc Compute the words prefixes at the end of an update 2021-04-27 14:39:52 +02:00
ab92c814c3 Fix attributes score 2021-04-27 14:35:43 +02:00
0ad9499b93 Fix an indexing bug in the words level positions 2021-04-27 14:35:43 +02:00
7aa5753ed2 Make the attribute positions range bounds to be fixed 2021-04-27 14:35:43 +02:00
658f316511 Introduce the Initial Criterion 2021-04-27 14:35:43 +02:00
89ee2cf576 Introduce the TreeLevel struct 2021-04-27 14:25:35 +02:00
bd1a371c62 Compute the WordsLevelPositions only once 2021-04-27 14:25:34 +02:00
8bd4f5d93e Compute the biggest values of the words_level_positions_docids 2021-04-27 14:25:34 +02:00
f713828406 Implement the clear and delete documents for the word-level-positions database 2021-04-27 14:25:34 +02:00
3069bf4f4a Fix and improve the words-level-positions computation 2021-04-27 14:25:34 +02:00
3a25137ee4 Expose and use the WordsLevelPositions update 2021-04-27 14:25:34 +02:00
c765f277a3 Introduce the WordsLevelPositions update 2021-04-27 14:25:34 +02:00
9242f2f1d4 Store the first word positions levels 2021-04-27 14:25:34 +02:00
b0a417f342 Introduce the word_level_position_docids Index database 2021-04-27 14:25:34 +02:00
75e7b1e3da Implement test Context methods 2021-04-27 14:25:34 +02:00
4ff67ec2ee Implement attribute criterion for small amounts of candidates 2021-04-27 14:25:34 +02:00
0f4c0beffd Introduce the Attribute criterion 2021-04-27 14:25:34 +02:00
f8dee1b402 [makes clippy happy] search/criteria/proximity.rs 2021-04-21 12:36:45 +02:00
6fa00c61d2 feat(search): support words_limit 2021-04-20 12:22:04 +03:00
c9b2d3ae1a Warn instead of returning an error when a conversion fails 2021-04-20 10:23:31 +02:00
2aeef09316 Remove debug logs while iterating through the facet levels 2021-04-20 10:23:31 +02:00
51767725b2 Simplify integer and float functions trait bounds 2021-04-20 10:23:31 +02:00
efbfa81fa7 Merge the Float and Integer enum variant into the Number one 2021-04-20 10:23:30 +02:00
33860bc3b7 test(update, settings): set & reset synonyms
fixes after review

more fixes after review
2021-04-18 11:24:17 +03:00
e39aabbfe6 feat(search, update): synonyms 2021-04-18 11:24:17 +03:00
9c4660d3d6 add tests 2021-04-15 16:25:56 +02:00
75464a1baa review fixes 2021-04-15 16:25:56 +02:00
2f73fa55ae add documentation 2021-04-15 16:25:55 +02:00
45c45e11dd implement distinct attribute
distinct can return error

facet distinct on numbers

return distinct error

review fixes

make get_facet_value more generic

fixes
2021-04-15 16:25:55 +02:00
dcb00b2e54 test a new implementation of the stop_words 2021-04-12 18:35:33 +02:00
da036dcc3e Revert "Integrate the stop_words in the querytree"
This reverts commit 12fb509d84.
We revert this commit because it's causing the bug #150.
The initial algorithm we implemented for the stop_words was:

1. remove the stop_words from the dataset
2. keep the stop_words in the query to see if we can generate new words by
   integrating typos or if the word was a prefix
=> This was causing the bug since, in the case of “The hobbit”, we were
   **always** looking for something starting with “t he” or “th e”
   instead of ignoring the word completely.

For now we are going to fix the bug by completely ignoring the
stop_words in the query.
This could cause another problem were someone mistyped a normal word and
ended up typing a stop_word.

For example imagine someone searching for the music “Won't he do it”.
If that person misplace one space and write “Won' the do it” then we
will loose a part of the request.

One fix would be to update our query tree to something like that:

---------------------
OR
  OR
    TOLERANT hobbit # the first option is to ignore the stop_word
    AND
      CONSECUTIVE   # the second option is to do as we are doing
        EXACT t	    # currently
        EXACT he
      TOLERANT hobbit
---------------------

This would increase drastically the size of our query tree on request
with a lot of stop_words. For example think of “The Lord Of The Rings”.

For now whatsoever we decided we were going to ignore this problem and consider
that it doesn't reduce too much the relevancy of the search to do that
while it improves the performances.
2021-04-12 18:35:33 +02:00
84c1dda39d test(http): setting enum serialize/deserialize 2021-04-08 17:03:40 +03:00
dc636d190d refactor(http, update): introduce setting enum 2021-04-08 17:03:40 +03:00
0a4bde1f2f update the default ordering of the criterion 2021-04-01 19:45:31 +02:00
2658c5c545 feat(index): update fields distribution in clear & delete operations
fixes after review

bump the version of the tokenizer

implement a first version of the stop_words

The front must provide a BTreeSet containing the stop words
The stop_words are set at None if an empty Set is provided
add the stop-words in the http-ui interface

Use maplit in the test
and remove all the useless drop(rtxn) at the end of all tests

Integrate the stop_words in the querytree

remove the stop_words from the querytree except if it was a prefix or a typo

more fixes after review
2021-04-01 19:12:35 +03:00
27c7ab6e00 feat(index): store fields distribution in index 2021-04-01 18:35:19 +03:00
12fb509d84 Integrate the stop_words in the querytree
remove the stop_words from the querytree except if it was a prefix or a typo
2021-04-01 13:57:55 +02:00
a2f46029c7 implement a first version of the stop_words
The front must provide a BTreeSet containing the stop words
The stop_words are set at None if an empty Set is provided
add the stop-words in the http-ui interface

Use maplit in the test
and remove all the useless drop(rtxn) at the end of all tests
2021-04-01 13:57:55 +02:00
9205b640a4 feat(index): introduce fields_ids_distribution 2021-03-31 18:44:47 +03:00
2cb32edaa9 fix(criterion): compile asc/desc regex only once
use once_cell instead of lazy_static

reorder imports
2021-03-30 16:07:14 +03:00
1e3f05db8f use fixed number of candidates as a threshold 2021-03-30 11:57:10 +03:00
a776ec9718 fix division 2021-03-29 19:16:58 +03:00
522e79f2e0 feat(search, criteria): introduce a percentage threshold to the asc/desc 2021-03-29 19:08:31 +03:00
9c27183876 fix broken offset 2021-03-15 20:23:50 +01:00