Details
-
Improvement
-
Resolution: Fixed
-
Critical
-
7.1.1
-
Security Level: Public
-
1
Description
Here's the scenario:
- Should the field be indexed with a custom analyzer within the FTS index.
- Allow a SEARCH function where the query is a match query over the field with a different analyzer.
Consistency will be guaranteed when the index is covering or not - since the analyzer context will be available during verification.
Note that if a custom analyzer is defined, the index name should be provided in the options of the SEARCH argument to obtain the the index mapping.
Additionally, it is perhaps good to drop the constraint that non-analytic queries require the keyword analyzer usage in definition and leave this up to the user to provide context correctly for the validation phase in case of non-covering indexes for queries. So that's essentially removing the restriction put in place with MB-39592.
Attachments
Issue Links
- relates to
-
MB-39592 [N1QL+FTS] Mandate keyword analyzer for queries that don't use an analyzer
- Closed
-
MB-41536 [N1QL+FTS] During verification set DefaultAnalyzer correctly in case "field" is not specified in FTS query
- Closed
-
MB-60258 N1QL queries with Search Functions starts failing randomly in between continuous query workload
- Closed