Re: Upserting doc fields from a SearchComponent

2017-02-01 Thread Charlie Hull
On 01/02/2017 15:55, Ugo Matrangolo wrote: Hi Erick, Personalizing a 'price' involves using an external service (luckily we could cache most of the interactions) and it is accessed using a lib that gets dropped in the Solr classpath. Hi Ugo, We built a Solr plugin 'XJoin', allowing you to use

Re: Upserting doc fields from a SearchComponent

2017-02-01 Thread Ugo Matrangolo
Hi Erick, Personalizing a 'price' involves using an external service (luckily we could cache most of the interactions) and it is accessed using a lib that gets dropped in the Solr classpath. What I need to do is this kind of flow: 1. Query (.. personalization params ...) 2. Find the initial sear

Re: Upserting doc fields from a SearchComponent

2017-02-01 Thread Erick Erickson
You need to be clear about what to do when. The [subquery], is completely separate from _finding_ the top N docs. Your last question is about finding the top N. There are really two choices that spring to mind, depending on where you keep your data about the user. Solr can't magically know that us

Re: Upserting doc fields from a SearchComponent

2017-02-01 Thread Ugo Matrangolo
Hi, tx for the speedy response. What if I need to filter on the result matches ?? Example: I have a price I need to personalize per user/request and need then to apply filter ranges on this personalized price (show only stuff in the 10$ - 99$ range). WDYT ? Best Ugo On Wed, Feb 1, 2017 at 3:3

Re: Upserting doc fields from a SearchComponent

2017-02-01 Thread Erick Erickson
If the data is from another Solr instance, consider the [subquery] Document Transformer here: https://cwiki.apache.org/confluence/display/solr/Transforming+Result+Documents#TransformingResultDocuments-[subquery] More broadly, you can write a custom DocTransformer plugin do insert anything you want