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

Add support for conversions boost term #933

Merged
merged 1 commit into from Jun 14, 2017

Conversation

sarchak
Copy link
Contributor

@sarchak sarchak commented Jun 13, 2017

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 :

  • organic banana:
    • Entity : banana
    • Attribute: organic

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

@ankane
Copy link
Owner

ankane commented Jun 14, 2017

Hey @sarchak, thanks for the PR, including tests 💯 Can we call it conversions_term since it's shorter?

@sarchak
Copy link
Contributor Author

sarchak commented Jun 14, 2017

@ankane by default term is used for dual purpose (match and boost) I, wanted to be very specific and tell that this would only be used for boosting. I am open to conversions_term but I think having the boost in the term will make it a bit clear for the user.

@ankane
Copy link
Owner

ankane commented Jun 14, 2017

Let's go with conversions_term, as everything around conversions deals with boosting, not matching.

Change conversions_boost_term to conversions_term
@sarchak sarchak force-pushed the sarchak/conversion_boost_term branch from d57cabe to 8887942 Compare June 14, 2017 19:50
@sarchak
Copy link
Contributor Author

sarchak commented Jun 14, 2017

Done!

@ankane ankane merged commit 5fcb7e5 into ankane:master Jun 14, 2017
@ankane
Copy link
Owner

ankane commented Jun 14, 2017

Looks great, thanks! 👍

sarchak added a commit to instacart/searchkick that referenced this pull request Jun 15, 2017
Change conversions_boost_term to conversions_term
mikelkew added a commit to mikelkew/searchkick that referenced this pull request Jul 18, 2017
* 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]
  ...
mikelkew added a commit to mikelkew/searchkick that referenced this pull request Jul 18, 2017
* 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]
  ...
mikelkew added a commit to mikelkew/searchkick that referenced this pull request Jul 18, 2017
* 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]
  ...
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants