* Moved NUM_SEARCHERS into a local variable
dynamically determined as the number of available cpus.
var name in lowercase (not a constant anymore).
updated it in docstring
* lowercased the varnames
* User can set number of logical cores in create_from_metas
* cargo fmt
* Num_searchers as Arc<AtomicUsize>
Retrieving the value with Relaxed ordering
Reverted create_from_metas signature. However, it calls num_cpus and
sets the Arc val
* Add skip information for posting list (skip to doc ids)
* Separate num bits from data for positions (skip n positions)
* Address in the position using a n-position offset
* Added a long skip structure to allow efficient opening of the position for a given term.
* Relocate `from_directory` closer to its usage
* Specific methods come before the generic method
* Rename open methods to follow the lead of the create methods
* Pull all creation methods next to each other
The goal here is to make it clear which methods are performing the
same function, and to assist with standardizing the API calls.
* Make `from_directory` private
This seems to be an internal function, so lets make it internal.
* Rename `create` to `create_in_dir`
This lets the name match the `create_in_ram` pattern and opens up
`create` for the generic implementation.
* Implement the generic create function
All of the create methods now delegate to the common create function
and future `create_in_*` functions now have a clear pattern
to follow as well
* Add non-deleted DocId iterator to SegmentReader
Closes#287
* Add Todo
* Add Unit Test
* Improving test based on feedback
- found bug and fixed it. :)
* Reestablish changes post rebase for clean merge
* Add fast field for associating arbitrary bytes to a document
* Fix unused macro_use warning
* Improvements from code review
* Make BytesFastFieldWriter public
* Fix json parsing validation failure
* Add bytes fast field to CHANGELOG.md
* Fix compile errors from merge
* Support merging
* Address misc code review comments
* Fix comments from CR
PhraseQuery panics with a nice error message when the underlying field does not have any positions.
The `QueryParser` fails as well with a dedicated error.
