Merge pull request #269 from FgForrest/dev

Regular update

README.md

@@ -174,9 +174,6 @@ you might encounter, and we'll try to fix them as soon as possible.
 - **evita_store**: binary serialization using Kryo library, persistent key/value datastore implementation
 - **evita_test_support**: utility classes that make writing integration tests with evitaDB easier
 - **jacoco**: Maven POM that allows to aggregate test coverage for entire project
-- **workaround**:
-  - **roaringBitmap**: workaround shaded build allowing to link RoaringBitmap libraries as a single "automatic Java module",
-    direct linking of original libraries leads to problems with Java module system
 
 # Quality requirements for the code
 

documentation/user/en/index.md

@@ -84,7 +84,7 @@ the first version to the general public.
    7. [Price](query/filtering/price.md)
    8. [References](query/filtering/references.md)
    9. [Hierarchy](query/filtering/hierarchy.md)
-   10. [Facet](query/filtering/special.md)
+   10. [Behavioral filter containers](query/filtering/behavioral.md)
 3. **Ordering**
    1. [Constant](query/ordering/constant.md)
    1. [Natural](query/ordering/natural.md)

documentation/user/en/query/basics.md

@@ -362,7 +362,7 @@ filtering of entities by the fact that they refer to a particular part of the tr
 Special constraints are used only for the definition of a filter constraint scope, which has a different treatment in 
 calculations:
 
-- [user filter](filtering/special.md#user-filter)
+- [user filter](filtering/behavioral.md#user-filter)
 
 ## Order by
 

documentation/user/en/query/filtering/special.md → documentation/user/en/query/filtering/behavioral.md

@@ -1,6 +1,9 @@
 ---
-title: Facet filtering
+title: Behavioral filtering containers
 date: '17.1.2023'
+perex: |
+  Special behavioral filtering constraint containers are used only for the definition of a filter constraint scope, 
+  which has a different treatment in calculations.
 author: 'Ing. Jan Novotný'
 proofreading: 'needed'
 ---

documentation/user/en/query/filtering/range.md

@@ -1,6 +1,10 @@
 ---
 title: Range filtering
 date: '17.1.2023'
+perex: |
+  Range filtering is used to filter entities by the value of their attributes that are of a range type. It allows you to
+  reduce the entity set to those entities whose range attribute includes the parameter value. If the parameter value is 
+  itself a range, only those entities with an overlapping range attribute will be matched.
 author: 'Ing. Jan Novotný'
 proofreading: 'needed'
 ---