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

Allow strings for setMinimumMatch in Terms query #1151

Merged
merged 2 commits into from
Jul 31, 2016

Conversation

topikito
Copy link
Contributor

This closes #1149

@ruflin
Copy link
Owner

ruflin commented Jul 27, 2016

LGTM. Can you also update the changelog?

@ruflin
Copy link
Owner

ruflin commented Jul 27, 2016

I'm curious why Travis did not start on this PR?

@topikito
Copy link
Contributor Author

@ruflin Sure, will do

@topikito
Copy link
Contributor Author

@ruflin Done

@topikito
Copy link
Contributor Author

Seems like Travis is now willing to test the changelog

/**
* @group unit
* @dataProvider provideMinimumArguments
Copy link
Owner

Choose a reason for hiding this comment

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

It would be nice to also have this for an integration test to make sure it also works with the current elasticsearch version. but we can add this in an other PR.

@ruflin ruflin merged commit 548b1d4 into ruflin:master Jul 31, 2016
@ruflin
Copy link
Owner

ruflin commented Jul 31, 2016

Merged. Thanks

@@ -7,6 +7,7 @@ All notable changes to this project will be documented in this file based on the

### Bugfixes
- Set HTTP headers on each request preventing server error if persistent connection is enabled and compression enabled and later disabled for the same connection.
- Removed `int` type hinting in `setMinimumMatch` (`Terms` Query): it should also allow `string`. [#1151](https://github.com/ruflin/Elastica/pull/1151)
Copy link
Owner

Choose a reason for hiding this comment

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

I will probably move this to improvements before the next release as I don't think it was a "bug". The limitation was more for historical reasons.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure - I just considered as a bug because the expected behaviour was not meeting the functional one.

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

Successfully merging this pull request may close these issues.

minimum_match accepts not only int but string
2 participants