Hi Shawn, No worries, and thanks for your clarification.
We make these changes in order to use the Unifed Highlighter, with hl.offsetSource = POSTING, and add "light" term vectors. The settings comes from what is written in the Solr guide on highlighting, which says the following: *Postings*: Supported by the Unified Highlighter. Set storeOffsetsWithPositions to true. This adds a moderate amount of extra data to the index but it speeds up highlighting tremendously, especially compared to analysis with longer text fields. However, wildcard queries will fall back to analysis unless "light" term vectors are added. - *with Term Vectors (light)*: Supported only by the Unified Highlighter. To enable this mode set termVectors to true but no other term vector related options on the field being highlighted. This adds even more data to the index than just storeOffsetsWithPositions but not as much as enabling all the extra term vector options. Term Vectors are only accessed by the highlighter when a wildcard query is used and will prevent a fall back to analysis of the stored text. This is definitely the fastest option for highlighting wildcard queries on large text fields. Below is the link to the guide: https://lucene.apache.org/solr/guide/7_5/highlighting.html Regards, Edwin On Tue, 29 Jan 2019 at 20:39, Shawn Heisey <apa...@elyograg.org> wrote: > On 1/29/2019 5:25 AM, Shawn Heisey wrote: > > Adding termVectors will make the index bigger. Potentially much bigger. > > This will increase the overall RAM requirement of the server, > > especially if the server is handling software other than Solr. Anything > > that makes the index bigger can affect performance. > > I misread the change. Apologies. Both definitions have termVectors. I > didn't notice it in the second definition because it was on a different > line than in the first one. > > After figuring out what you changed, I cannot figure out what it is > you're trying to do, and I'm not sure that the settings make sense. > You've added/changed these three settings: > > storeOffsetsWithPositions="true" > termPositions="false" > termOffsets="false" > > It seems to me that the first new setting is directly contrary to the > other two new settings. I really have no idea what the outcome of the > changes will be. > > Thanks, > Shawn >
