DOC-9450: Update SEARCH_META(..) instructions and examples #2469
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
|
I don't see how this PR fixes the broken links mentioned in DOC-9450? |
abhinavdangeti
force-pushed
the
DOC9450-7.1
branch
5 times, most recently
from
ddeae34 to
8561ae5
Compare
Thejas-bhat
reviewed
Feb 21, 2022
|
|
||
| [NOTE] | ||
| -- | ||
| The examples in this page all assume that demonstration full text indexes have been created. | ||
| The examples in this page assume that you have a full text search index created with this definition, unless specified otherwise .. |
There was a problem hiding this comment.
Suggested change
| The examples in this page assume that you have a full text search index created with this definition, unless specified otherwise .. | |
| The examples in this page assume that you have a full text search index created with this definition, unless specified otherwise. |
| @@ -350,8 +392,74 @@ WHERE t1.type = "hotel" AND SEARCH(t1.description, "amazing"); | |||
| ---- | |||
|
|
|||
| If the full text search index being queried has its default mapping disabled and has a custom type mapping defined, the query needs to specify the type explicitly. | |||
|
|
|||
| //The above query uses the demonstration index xref:fts:fts-demonstration-indexes.adoc#travel-sample-index-hotel-description[travel-sample-index-hotel-description], which has the custom type mapping "hotel". | |||
| The above query uses the following index definition .. | |||
There was a problem hiding this comment.
Suggested change
| The above query uses the following index definition .. | |
| The above query uses the following index definition: |
| For more information, refer to xref:fts:fts-quickstart-guide.adoc#preparing-for-full-text-searches[Preparing for Full Text Searches]. | ||
|
|
||
| [NOTE] | ||
| -- | ||
| The examples in this page all assume that demonstration full text indexes have been created, as described in xref:fts:fts-demonstration-indexes.adoc[Demonstration Indexes]. | ||
| The examples in this page assume that you have a full text search index created with this definition, unless specified otherwise .. |
There was a problem hiding this comment.
Suggested change
| The examples in this page assume that you have a full text search index created with this definition, unless specified otherwise .. | |
| The examples in this page assume that you have a full text search index created with this definition, unless specified otherwise. |
| @@ -358,7 +400,74 @@ WHERE t1.type = "hotel" AND SEARCH(t1.description, "amazing"); | |||
| ---- | |||
|
|
|||
| If the full text search index being queried has its default mapping disabled and has a custom type mapping defined, the query needs to specify the type explicitly. | |||
| The above query uses the demonstration index xref:fts:fts-demonstration-indexes.adoc#travel-sample-index-hotel-description[travel-sample-index-hotel-description], which has the custom type mapping "hotel". | |||
| The above query uses the following index definition .. | |||
There was a problem hiding this comment.
Suggested change
| The above query uses the following index definition .. | |
| The above query uses the following index definition: |
|
Another small suggestion is perhaps having consistent index definition examples wherever possible. This is in reference to index definitions on line 19 and 403 (in searchfun.adoc and similarly on lines 13 and 395 in fts-searching-from-N1QL.adoc) which differ in sourceType and the segmentVersion specified. |
abhinavdangeti
force-pushed
the
DOC9450-7.1
branch
from
8561ae5 to
aaaa6e6
Compare
|
A forward merge should cover this. |
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.