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

Remove some more ParseFieldMatcher usages #22571

Conversation

javanna
Copy link
Member

@javanna javanna commented Jan 11, 2017

Remove some more ParseFieldMatcher usages

Relates to #19552
Relates to #22130

@javanna
Copy link
Member Author

javanna commented Jan 11, 2017

@nik9000 This should be the second last PR on this topic, next one will be the actual removal I think.

Copy link
Member

@nik9000 nik9000 left a comment

Choose a reason for hiding this comment

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

Left a variable naming thing but otherwise LGTM.

ADD_PARSER.declareField(AliasActions::routing, p -> p.text(), new ParseField("routing"), ValueType.INT);
ADD_PARSER.declareField(AliasActions::indexRouting, p -> p.text(), new ParseField("index_routing"), ValueType.INT);
ADD_PARSER.declareField(AliasActions::searchRouting, p -> p.text(), new ParseField("search_routing"), ValueType.INT);
ADD_PARSER.declareField(AliasActions::routing, XContentParser::text, new ParseField("routing"), ValueType.INT);
Copy link
Member

Choose a reason for hiding this comment

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

++

static {
PARSER.declareField((parser, request, parseFieldMatcherSupplier) ->
request.getShrinkIndexRequest().settings(parser.map()),
PARSER.declareField((parser, request, parseFieldMatcherSupplier) -> request.getShrinkIndexRequest().settings(parser.map()),
Copy link
Member

Choose a reason for hiding this comment

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

s/parseFieldMatcherSupplier/context/ ? Or is there a version of this method without context?

Copy link
Member Author

Choose a reason for hiding this comment

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

leftover thanks for finding it.

@javanna javanna force-pushed the enhancement/remove_parse_field_matcher_usages_5 branch from 81ec2bf to 6099ef4 Compare January 12, 2017 09:02
@javanna javanna merged commit 0f7d52d into elastic:master Jan 12, 2017
javanna added a commit to javanna/elasticsearch that referenced this pull request Jan 12, 2017
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.

2 participants