Or a Jira to document it. The basic idea is that if a normal leading wildcard is too slow, the user can index a copy of their text fields using the text_rev type, which indexes terms with their characters reversed and with a special marker. Then the query parser detects a leading wildcard and that the field type uses the reversed wildcard filter, and then it generates a wildcard query that using the reversed query token and wildcard pattern so that the leading wildcard becomes a trailing wildcard or prefix query
-- Jack Krupansky On Fri, Jan 9, 2015 at 3:15 PM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > Anybody? Otherwise, I guess it is a JIRA to delete the unused field? > > Regards, > Alex. > ---- > Sign up for my Solr resources newsletter at http://www.solr-start.com/ > > > On 28 December 2014 at 13:16, Alexandre Rafalovitch <arafa...@gmail.com> > wrote: > > I am looking at the collection1/techproducts schema and I can't figure > > out how the reversed wildcard example is supposed to work. > > > > We define text_general_rev type and text_rev field, but we don't seem > > to be populating it at any point. And running the example does not > > seem to show any tokens in the field even when the non-inverted text > > field does have some. > > > > Apparently, there is some magic in the QueryParser to do something > > about this at query time, but I see no explanation of what is supposed > > to happen at the index/schema time. > > > > Anybody has the skinny on this one? > > > > Regards, > > Alex. > > ---- > > Sign up for my Solr resources newsletter at http://www.solr-start.com/ >