Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

[N1QL+FTS] During verification set DefaultAnalyzer correctly in case "field" is not specified in FTS query

Description

Non-covering queries when the field name isn't specified - needs the query to look into the _all field (if available).

As part of verification - in this situation we will need to set the analyzer for the default mapping correctly so non-analytic queries work correctly (keyword analyzer).

Example index definition:

{ "type": "fulltext-index", "name": "default", "uuid": "558d7e033dff989e", "sourceType": "couchbase", "sourceName": "default", "sourceUUID": "37ad8b8f5d53e38f4fff0bbbc9175671", "planParams": { "maxPartitionsPerPIndex": 171, "indexPartitions": 6 }, "params": { "doc_config": { "docid_prefix_delim": "", "docid_regexp": "", "mode": "type_field", "type_field": "type" }, "mapping": { "analysis": {}, "default_analyzer": "standard", "default_datetime_parser": "dateTimeOptional", "default_field": "_all", "default_mapping": { "dynamic": true, "enabled": false }, "default_type": "_default", "docvalues_dynamic": true, "index_dynamic": true, "store_dynamic": false, "type_field": "_type", "types": { "hotel": { "default_analyzer": "keyword", "dynamic": true, "enabled": true } } }, "store": { "indexType": "scorch" } }, "sourceParams": {} }

Example query:

SELECT * FROM default AS d WHERE d.type='hotel' and search (d, {"query":{"wildcard":"*garden*"}}) limit 1;

 

The workaround without a fix is to use the field setting within the query.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

Activity

Show:

Girish Benakappa November 17, 2020 at 10:05 PM

Verified in 6.6.1-9060 and 7.0.0 build 3739

CB robot September 17, 2020 at 5:33 PM

Build couchbase-server-7.0.0-3145 contains n1fty commit 1499e8d with commit message:
https://couchbasecloud.atlassian.net/browse/MB-41536#icft=MB-41536: Set defaultAnalyzer appropriately during verify/eval

CB robot September 17, 2020 at 4:53 PM

Build couchbase-server-6.6.1-9060 contains n1fty commit 1499e8d with commit message:
https://couchbasecloud.atlassian.net/browse/MB-41536#icft=MB-41536: Set defaultAnalyzer appropriately during verify/eval

Abhi Dangeti September 17, 2020 at 4:44 PM

Fix should be available for 6.6.1 builds.

While the fix has been merged into cheshire-cat builds, we'll still see this issue until we add go.mod for n1fty and n1fty uses the right version of bleve which includes the fix for https://couchbasecloud.atlassian.net/browse/MB-38957#icft=MB-38957.

Abhi Dangeti September 17, 2020 at 4:09 PM

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created September 17, 2020 at 4:03 PM
Updated June 28, 2023 at 7:16 PM
Resolved September 17, 2020 at 4:44 PM
Configure
Instabug