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

Add PathHierarchy type back to path_hierarchy tokenizer for backward compatibility with 1.x #15785

Merged
merged 1 commit into from
Jan 6, 2016

Conversation

ywelsch
Copy link
Contributor

@ywelsch ywelsch commented Jan 6, 2016

Relates to #15756

@jpountz
Copy link
Contributor

jpountz commented Jan 6, 2016

Is there a way that we could only support it for indices created before 2.0 to ensure that new indices will use the lowercase version?

@jpountz
Copy link
Contributor

jpountz commented Jan 6, 2016

Maybe we could register a subclass of PathHierarchyTokenizerFactory whose constructor fails if the version in the index settings is >= 2.0? The error message could even point to the replacement to use?

@jpountz
Copy link
Contributor

jpountz commented Jan 6, 2016

Hmm after all we will have to do it for others analysis components (eg. edgeNGram) so let's push it as-is and work on a migration path as part of #8988

ywelsch pushed a commit that referenced this pull request Jan 6, 2016
Add PathHierarchy type back to path_hierarchy tokenizer for backward compatibility with 1.x
@ywelsch ywelsch merged commit e0599bf into elastic:master Jan 6, 2016
ywelsch pushed a commit that referenced this pull request Jan 6, 2016
ywelsch pushed a commit that referenced this pull request Jan 6, 2016
ywelsch pushed a commit that referenced this pull request Jan 6, 2016
ywelsch pushed a commit that referenced this pull request Jan 6, 2016
@s1monw
Copy link
Contributor

s1monw commented Jan 6, 2016

@ywelsch this went into 2.2 as well can you label it accordingly?

@ywelsch
Copy link
Contributor Author

ywelsch commented Jan 6, 2016

@s1monw done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants