docs: add json to full text search document #4865
Open
+132
−4
Conversation
This file contains hidden or 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
1397aa7 to
98dbbab
Compare
|
Hi @jackye1995 , could you help review this document update when you have time, thanks very much! |
jackye1995
reviewed
Oct 2, 2025
|
|
||
| The full text search index supports multiple tokenizer types for different text processing needs: | ||
| The full text search index supports multiple tokenizer types for different text processing needs. | ||
| There are two different tokenizer configurations: ```lance_tokenizer``` and ```base_tokenizer```. |
There was a problem hiding this comment.
no need to do triple backquotes, single backquotes are fine.
jackye1995
reviewed
Oct 2, 2025
|
|
||
| #### Text Tokenizer | ||
| Text Tokenizer is responsible for handling TEXT-type data, which is Utf8, LargeUtf8 or List of them in arrow format. | ||
| The Text Tokenizer behaves consistently in both "query" and "document parsing" scenarios, which means that if a document |
There was a problem hiding this comment.
I don't think we need double quotes for "query" and "document parsing"
There was a problem hiding this comment.
also same comment to a few other cases below
jackye1995
reviewed
Oct 2, 2025
| #### Text Tokenizer | ||
| Text Tokenizer is responsible for handling TEXT-type data, which is Utf8, LargeUtf8 or List of them in arrow format. | ||
| The Text Tokenizer behaves consistently in both "query" and "document parsing" scenarios, which means that if a document | ||
| contains the word "lance," we can retrieve it using a query with "lance." |
jackye1995
reviewed
Oct 2, 2025
| age,number,30 | ||
| address.city,str,San | ||
| address.city,str,Francisco | ||
| address.zip,number,94102 |
There was a problem hiding this comment.
should define and handle what if the document path contains . or : for parsing and querying
There was a problem hiding this comment.
Thanks your nice suggestion! I have updated the example, adding . and : to json text with the corresponding triplets. I also added a unit test to . and :.
98dbbab to
7fb8468
Compare
e1bbd02 to
9e66d90
Compare
9e66d90 to
d7c83b0
Compare
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.