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 support for conversions boost term #933
Conversation
Hey @sarchak, thanks for the PR, including tests 💯 Can we call it |
@ankane by default |
Let's go with |
Change conversions_boost_term to conversions_term
d57cabe
to
8887942
Compare
Done! |
Looks great, thanks! 👍 |
Change conversions_boost_term to conversions_term
* commit '9c957ffd9a6bc5c356ead1ea445cac2e9b6d4369': (25 commits) Prefer default_fields if specified [skip ci] Use Elasticsearch 5.5 as default for tests [skip ci] Upgraded ES6 test version [skip ci] Clarify error message [skip ci] Ensure _all isn't indexed in ES 6 [skip ci] Added _all and default_fields options Version bump to 2.3.1 Updated changelog [skip ci] Don't call minimum twice, and handle no record case better Switch to find_in_batches and find the first PK to see if's a Numeric Clarify filterable and add test Updated filterable docs [skip ci] Correctly pass the id of the batch Remove un-necessary search information from the Sku model Reindex non-numerical PK's in batches Add failing test for non-integer primary key models Updated readme for conversions_term [skip ci] Add support for conversions boost term (ankane#933) Fixed page_view_entries for Kaminari - fixes ankane#934 Added test for no fields [skip ci] ...
* master: (26 commits) Prefer default_fields if specified [skip ci] Use Elasticsearch 5.5 as default for tests [skip ci] Upgraded ES6 test version [skip ci] Clarify error message [skip ci] Ensure _all isn't indexed in ES 6 [skip ci] Added _all and default_fields options Version bump to 2.3.1 Updated changelog [skip ci] Don't call minimum twice, and handle no record case better Switch to find_in_batches and find the first PK to see if's a Numeric Clarify filterable and add test Updated filterable docs [skip ci] Correctly pass the id of the batch Remove un-necessary search information from the Sku model Reindex non-numerical PK's in batches Add failing test for non-integer primary key models Updated readme for conversions_term [skip ci] Add support for conversions boost term (ankane#933) Fixed page_view_entries for Kaminari - fixes ankane#934 Added test for no fields [skip ci] ...
* master: (26 commits) Prefer default_fields if specified [skip ci] Use Elasticsearch 5.5 as default for tests [skip ci] Upgraded ES6 test version [skip ci] Clarify error message [skip ci] Ensure _all isn't indexed in ES 6 [skip ci] Added _all and default_fields options Version bump to 2.3.1 Updated changelog [skip ci] Don't call minimum twice, and handle no record case better Switch to find_in_batches and find the first PK to see if's a Numeric Clarify filterable and add test Updated filterable docs [skip ci] Correctly pass the id of the batch Remove un-necessary search information from the Sku model Reindex non-numerical PK's in batches Add failing test for non-integer primary key models Updated readme for conversions_term [skip ci] Add support for conversions boost term (ankane#933) Fixed page_view_entries for Kaminari - fixes ankane#934 Added test for no fields [skip ci] ...
Why?
Currently, when boosting on conversions we use the term for boosting. This PR will add support to have separate conversion boost term.
One way to improve search results is if we can have separate terms for matching and boosting.
Example :
We need a way to use the existing conversions for boosting (using popularity for boosting) and be more flexible with matching. In our case match would be with "banana" and conversions boosting will be with "organic banana"
cc @ankane @meetrajesh