upgrade to blevesearch/bleve v2 #5
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
depending on the analyzer used, it is possible for the search term itself to contain characters which should be escaped before generating html output. this commit adds escaping on the term itself, and adds some unit tests as well.
+ Update the the yacc rules while parsing query string syntax to
accommodate a "phrase" as a field name. This will allow for the
user to use field names that have white spaces in them.
For example:
- Index definition has a field "with JSON" searchable as "with JSON"
- With a match query - {"field": "with JSON", "match": "reserved"}
- This is previously not supported within the query string syntax,
but is now possible ..
+------------------------+
| "with JSON":"reserved" |
+------------------------+
+ query_string.y.go is generated using goyacc based on new rules added
to query_string.y.
+ This addresses https://issues.couchbase.com/browse/MB-41264.
+ This helps de-duplicate all the new rules introduced for interpreting field name as a phrase.
* refactor to remove circular deps * reduce index and segment API surface area * update Advanced() method (#1509) * relocate store pkg inside upsidedown (#1510) * remove Advanced() method from scorch (#1511) * remove use of dump methods from index reader (#1516) * remove remaining blevex imports (#1520) * update analysis.TokenFrequency to use options (#1522) * switch default index to scorch with latest zap (#1528) * MatchOperator should be that type instead of int (#1410) Co-authored-by: Sreekanth Sivasankaran <sreekanth.sivasankaran@couchbase.com> Co-authored-by: Mario de Frutos Dieguez <mario@defrutos.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.