Skip to content

flex-indexes.adoc small corrections #2699

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 1, 2024
Merged

flex-indexes.adoc small corrections #2699

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions modules/n1ql/pages/n1ql-language-reference/flex-indexes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ Some of the main differences are described here.

* N1QL uses escaped path names, whereas full-text indexes flatten the field names.

* N1QL uses array subscripts to identify array objects, for example `1.arr1[0].b`; whereas full-text indexes ignore subscripts, for example `f1.arr1.b`.
* N1QL uses array subscripts to identify array objects, for example `f1.arr1[0].b`; whereas full-text indexes ignore subscripts, for example `f1.arr1.b`.
This means full-text indexes cannot uniquely identify the path.

* In N1QL, data can be compared across data types.
Expand Down Expand Up @@ -90,7 +90,7 @@ For further details, refer to {build-index}[BUILD INDEX].

Assuming that there is no search function in the query predicate, there are two ways to specify that you would like to use a full-text index with a N1QL query:

* Use the `USE FTS` hint in the N1QL query.
* Use the `USING FTS` hint in the N1QL query.
For full details, refer to {index-type}[USE Clause].

* Set the `use_fts` request-level parameter to `true`.
Expand Down Expand Up @@ -787,4 +787,4 @@ Refer to <<n1ql-predicates>> above.
[[pagination]]
=== ORDER, LIMIT, and OFFSET

The LIMIT, OFFSET, and ORDER clauses can be used with a full-text index when the index uses the default type mapping or a single custom type mapping.
The LIMIT, OFFSET, and ORDER clauses can be used with a full-text index when the index uses the default type mapping or a single custom type mapping.