bq: Is there a way to search the global copyField but highlight the original stored fields?
That's what I was suggesting. Specify the global field for your search, but use hl.fl for fields you want to copy. And yes, storing the fields is required for highlighting. Consider stemming (or worse, phonetic tokens). If you didn't store the fields, you'd have to work with the analyzed tokens and display _those_, which would be puzzling at best to a user. Best, Erick On Wed, Jul 30, 2014 at 2:34 PM, Manuel Le Normand < manuel.lenorm...@gmail.com> wrote: > The slowdown occurs during search, not highlighting. Having a disjunctive > query with 50 terms running 20 different posting lists is a hard task. > Harder than searching these 50 terms on a single (larger) posting list as > in the copyField case. > > With the edismax qf param, sure, hl.fl=* works as it should. In the > copyField case it does not as it is a non stored field. There are no > higlights on non stored fields AFAIK. > > Is there a way to search the global copyField but highlight the original > stored fields? > > > On Wed, Jul 30, 2014 at 5:54 PM, Erick Erickson <erickerick...@gmail.com> > wrote: > > > Doesn't hl.fl work in this case? Or is highlighting the 10 fields the > > slowdown? > > > > Best, > > Erick > > > > > > On Wed, Jul 30, 2014 at 2:55 AM, Manuel Le Normand < > > manuel.lenorm...@gmail.com> wrote: > > > > > Current I use the classic but I can change my posting format in order > to > > > work with another highlighting component if that leads to any solution > > > > > >
