-
Notifications
You must be signed in to change notification settings - Fork 184
DOC-9450: Update SEARCH_META(..) instructions and examples #2468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I don't see how this PR fixes the broken links mentioned in DOC-9450? |
@simon-dew One of the links was already fixed previously, as for the other - the page was deleted. So let me push up another patch set overwriting the earlier with the necessary examples. |
d4bd35e
to
401a3f0
Compare
|
||
[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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The above query uses the following index definition .. | |
The above query uses the following index definition: |
Perhaps, we can have 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. |
Ya good point, let me update the patchset. |
401a3f0
to
b33e8d6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note we previously had fts-demonstration-indexes.adoc which is still in 6.6 it becomes https://docs.couchbase.com/server/6.6/fts/fts-demonstration-indexes.html
the page has been removed in the recent updates.
Perhaps we should put it back as we reference this missing page from two additional documents outside this update which results in dead links
find . -name '*.adoc' -exec grep -l :fts-demonstration-indexes {} ;
- ./docs-server/modules/n1ql/pages/n1ql-language-reference/searchfun.adoc
- ./docs-server/modules/fts/pages/fts-searching-from-N1QL.adoc
- ./docs-server/modules/fts/pages/fts-quickstart-guide.adoc
- ./docs-server/modules/fts/pages/fts-supported-queries-geo-spatial.adoc
Items 1. and 2. are fixed in this PR
Item 3. Is a commented out reference - it should be deleted (it is a false positive via find)
Item 4. requires some minor work on fts-supported-queries-geo-spatial.adoc to remove "See Demonstration Indexes for the body" as the target no longer exists.
This will still leaves us with potential off site references to the missing page "fts-demonstration-indexes.adoc" but our docs will be consistent.
@jon-strabala Let me push up a patch here removing references to As for adding the dropped page back ..
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.