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 much ceremony from parsing client yaml test suites #22311

Merged
merged 5 commits into from Dec 22, 2016

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Dec 21, 2016

  • Remove a checked exception, replacing it with ParsingException.
  • Remove all Parser classes for the yaml sections, replacing them with static methods.
  • Remove ClientYamlTestFragmentParser. Isn't used any more.
  • Remove ClientYamlTestSuiteParseContext, replacing it with some static utility methods.

I did not rewrite the parsers using ObjectParser because I don't think it is worth it right now.

@nik9000 nik9000 added review >test Issues or PRs that are addressing/adding tests v5.2.0 v6.0.0-alpha1 labels Dec 21, 2016
@nik9000
Copy link
Member Author

nik9000 commented Dec 21, 2016

Another cleanup PR that came from #22003. @rjernst, @imotov, @javanna, @martijnvg, or anyone else, want to have a look?

Copy link
Member

@javanna javanna left a comment

Choose a reason for hiding this comment

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

LGTM assuming that tests run, all the parsing code has been copied over to their corresponding new static methods unchanged, and that all the parsing tests have been kept around as well. It is hard to double check all that in the PR, review based on trust :)

@nik9000
Copy link
Member Author

nik9000 commented Dec 22, 2016

LGTM assuming that tests run, all the parsing code has been copied over to their corresponding new static methods unchanged, and that all the parsing tests have been kept around as well.

Yup, that is pretty much what I did. Thanks for the review! I'll rerun the tests and if they pass again I'll merge.

@nik9000 nik9000 merged commit f5f2149 into elastic:master Dec 22, 2016
@nik9000
Copy link
Member Author

nik9000 commented Dec 22, 2016

Thanks for reviewing @javanna!

master: f5f2149
5.x: ee09172

jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request Dec 22, 2016
* master: (22 commits)
  Support negative numbers in writeVLong (elastic#22314)
  UnicastZenPing's PingingRound should prevent opening connections after being closed
  Add task to clean idea build directory. Make cleanIdea task invoke it.
  add trace logging to UnicastZenPingTests.testResolveReuseExistingNodeConnections
  Adds ingest processor headers to exception for unknown processor. (elastic#22315)
  Remove much ceremony from parsing client yaml test suites (elastic#22311)
  Support numeric bounds with decimal parts for long/integer/short/byte datatypes (elastic#21972)
  inner hits: Don't inline inner hits if the query the inner hits is inlined into can't resolve mappings and ignore_unmapped has been set to true
  Fix stackoverflow error on InternalNumericMetricAggregation
  Date detection should not rely on a hardcoded set of characters. (elastic#22171)
  `value_type` is useful regardless of scripting. (elastic#22160)
  Improve concurrency of ShardCoreKeyMap. (elastic#22316)
  fixed jdocs and removed already fixed norelease
  Adds abstract test classes for serialisation (elastic#22281)
  Introduce translog no-op
  Provide helpful error message if a plugin exists
  Clear static variable after suite
  Repeated language analyzers (elastic#22240)
  Restore deprecation warning for invalid match_mapping_type values (elastic#22304)
  Make `-0` compare less than `+0` consistently. (elastic#22173)
  ...
nik9000 added a commit that referenced this pull request Dec 22, 2016
* Remove a checked exception, replacing it with `ParsingException`.
* Remove all Parser classes for the yaml sections, replacing them with static methods.
* Remove `ClientYamlTestFragmentParser`. Isn't used any more.
* Remove `ClientYamlTestSuiteParseContext`, replacing it with some static utility methods.

I did not rewrite the parsers using `ObjectParser` because I don't think it is worth it right now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Issues or PRs that are addressing/adding tests v5.2.0 v6.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants