Skip to content
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

Inheriting the correct analyzer when default mapping is in use #1807

Merged
merged 1 commit into from
Apr 5, 2023

Conversation

abhinavdangeti
Copy link
Member

Here's an unhandled situation:

  • Say one defines a default dynamic mapping with a non-standard analyzer
  • Field content is indexed correctly per this non-standard analyzer
  • But, now let them run an analytic query over a field (that exists) - - This analytic query is incorrectly pulling the definition from the index's default_analyzer (standard) as opposed to the non-standard analyzer.

This situation is not handled properly only for the default mapping and not type mappings.

Also, https://issues.couchbase.com/browse/MB-56306

Here's an unhandled situation:
- Say one defines a default dynamic mapping with a non-standard analyzer
- Field content is indexed correctly per this non-standard analyzer
- But, now let them run an analytic query over a field (that exists) -
    - This analytic query is incorrectly pulling the definition from the
      index's default_analyzer (`standard`) as opposed to the
      non-standard analyzer.

This situation is not handled properly only for the default mapping and
not type mappings.

Also, https://issues.couchbase.com/browse/MB-56306
@abhinavdangeti abhinavdangeti requested a review from a team April 4, 2023 18:37
@abhinavdangeti abhinavdangeti added this to the v2.3.8 milestone Apr 4, 2023
@abhinavdangeti abhinavdangeti merged commit 0c48a9e into master Apr 5, 2023
@abhinavdangeti abhinavdangeti deleted the mb56306 branch April 5, 2023 14:22
abhinavdangeti added a commit that referenced this pull request Apr 5, 2023
Here's an unhandled situation:
- Say one defines a default dynamic mapping with a non-standard analyzer
- Field content is indexed correctly per this non-standard analyzer
- But, now let them run an analytic query over a field (that exists) -
    - This analytic query is incorrectly pulling the definition from the
      index's default_analyzer (`standard`) as opposed to the
      non-standard analyzer.

This situation is not handled properly only for the default mapping and
not type mappings.

Also, https://issues.couchbase.com/browse/MB-56306
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants