I'm wondering if storing just the offset as a payload would be cheaper from storage perspective than enabling termOffsets, termVectors and termPositions? Maybe we could get the offset info to return with results from there then?
Thanks, Nalini On Fri, Sep 20, 2013 at 5:02 PM, Nalini Kartha <nalinikar...@gmail.com>wrote: > Thanks for the reply. > > We tried enabling these options but that's also causing too much index > bloat so I was wondering if there's a way to get at the offset information > more cheaply? > > Thanks, > Nalini > > > On Fri, Sep 20, 2013 at 4:41 PM, Jack Krupansky > <j...@basetechnology.com>wrote: > >> Set: >> >> termVectors=true >> termPositions=true >> termOffsets=true >> >> And use the fast vector highlighter. >> >> -- Jack Krupansky >> >> -----Original Message----- From: Nalini Kartha Sent: Friday, September >> 20, 2013 7:34 PM To: solr-user@lucene.apache.org Subject: Getting term >> offsets from Solr >> Hi, >> >> We're looking at implementing highlighting for some fields which may be >> too >> large to store in the index. >> >> As an alternative to using the Solr Highlighter (which needs fields to be >> stored), I was wondering if a) the offsets of terms are stored BY DEFAULT >> in the index (even if we're not using the TermVectorComponent) and if so, >> b) is there a way to get the offset information from Solr. >> >> Thanks, >> Nalini >> > >
