FWIW I tried this on the techproducts schema with a modification to the name field, but did not see the issue.
I suspect you did not re-index after making these schema changes. If you did, then also check that the collection (or core) truly started fresh (never had any previous schema) because if you tried it one way then merely deleted/replaced the documents after changing the schema, then some internal metadata in the underlying index data tends to persist. I suspect some of the options flipped here might stay sticky. If that really isn't it, then you might suggest to me exactly how to reproduce this from what Solr ships with, like the techproducts example schema and dataset. ~ David On Sun, Jul 21, 2019 at 10:07 PM Richard Walker <richard.wal...@ardc.edu.au> wrote: > On 22 Jul 2019, at 11:32 am, Richard Walker <richard.wal...@ardc.edu.au> > wrote: > > I'm trying out the advice in the user guide > > ( > https://lucene.apache.org/solr/guide/8_1/highlighting.html#schema-options-and-performance-considerations > ) > > for using the unified highlighter. > > > > ... > > * "set storeOffsetsWithPositions to true" > > * "set termVectors to true but no other term vector > > related options on the field being highlighted" > ... > > I completely forgot to mention that I also tried _just_: > > > * "set storeOffsetsWithPositions to true" > > i.e., without _also_ setting termVectors, and this _doesn't_ > give the exception. > > So it seems to be the _combination_ of: > * unified highlighter > * storeOffsetsWithPositions > * termVectors > > that seems to be giving the exception. > >
