Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Enhancement, add the field type conflict check in semantic check #470

Merged

Conversation

penghuo
Copy link
Contributor

@penghuo penghuo commented May 15, 2020

Issue #, if available: #348, #445

Description of changes:

  • Add wildcard index handing in semantic. If the field is used in query have conflict type in wildcard index, semantic exception will be thrown.
  • The mapping conflict resolver logic in the TermFieldRewriter has been refined to do the lazy evaluation only when the field is accessed.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Copy link
Member

@dai-chen dai-chen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just minor comment. Thanks for this important improvement!

import org.junit.Test;
import org.junit.rules.ExpectedException;

import static org.junit.Assert.*;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

np: wildcard import

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@abbashus abbashus merged commit bda0b47 into opendistro-for-elasticsearch:master May 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
4 participants