Skip to content

SearchResponse#fromXContent to not require START_OBJECT as current token#24794

Merged
javanna merged 1 commit intoelastic:feature/client_aggs_parsingfrom
javanna:fix/search_response_parsing
May 19, 2017
Merged

SearchResponse#fromXContent to not require START_OBJECT as current token#24794
javanna merged 1 commit intoelastic:feature/client_aggs_parsingfrom
javanna:fix/search_response_parsing

Conversation

@javanna
Copy link
Copy Markdown
Contributor

@javanna javanna commented May 19, 2017

The method should rather advance one token and only then require a START_OBJECT as the current token. This allows to parse given a parser that's at the beginning of the response, where the initial/current token is null.

The method should rather advance one token and only then require a START_OBJECT as the current token. This allows to parse given a parser that's at the beginning of the response, where the initial/current token is null.
Copy link
Copy Markdown
Member

@cbuescher cbuescher left a comment

Choose a reason for hiding this comment

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

LGTM

@javanna javanna merged commit 0b8da31 into elastic:feature/client_aggs_parsing May 19, 2017
javanna added a commit to javanna/elasticsearch that referenced this pull request May 23, 2017
…ken (elastic#24794)

The method should rather advance one token and only then require a START_OBJECT as the current token. This allows to parse given a parser that's at the beginning of the response, where the initial/current token is null.
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.

3 participants