Feature/#204 timings optimizations
Feature
Summary
This MR provides improved query timings by using the range index.
timings before
"query": "مقصور*"
"took": 5265,
"took": 5380,
"took": 5544,
"took": 5663,timings after
"took": 647,
"took": 648,
"took": 607,
"took": 794,
"took": 596,
"took": 622,
"took": 571,
"took": 585,Compliance to “Definition of Done”
-
Unit tests passed -
Code reviewed -
Product Owner accepts the User Story
Documentation
-
I updated the README (if applicable) -
I provided my functions with appropriate documentation -
I updated existing documentation
Tests
Are we able to test this new feature?
-
Yes, everything can be done via unit tests. -
Yes, you can test by following these steps: … -
No, it is not possible.
Changelog
-
I added a statement to the CHANGELOG.
Version number
-
I bumped the version number in build.properties.
Closes
Closes #204 (closed)