So copyField it to another and apply alternative processing there. Use
eDismax to search both. No need to store the copied field, just index it.
Regards,
Alex
On 16/07/2014 2:46 am, "Hayden Muhl" <haydenm...@gmail.com> wrote:
> Both fields? There is only one field here: username.
>
>
> On Mon, Jul 14, 2014 at 6:17 PM, Alexandre Rafalovitch <arafa...@gmail.com
> >
> wrote:
>
> > Search against both fields (one split, one not split)? Keep original
> > and tokenized form? I am doing something similar with class name
> > autocompletes here:
> >
> >
> https://github.com/arafalov/Solr-Javadoc/blob/master/JavadocIndex/JavadocCollection/conf/schema.xml#L24
> >
> > Regards,
> > Alex.
> > Personal: http://www.outerthoughts.com/ and @arafalov
> > Solr resources: http://www.solr-start.com/ and @solrstart
> > Solr popularizers community: https://www.linkedin.com/groups?gid=6713853
> >
> >
> > On Tue, Jul 15, 2014 at 8:04 AM, Hayden Muhl <haydenm...@gmail.com>
> wrote:
> > > I'm working on using Solr for autocompleting usernames. I'm running
> into
> > a
> > > problem with the wildcard queries (e.g. username:al*).
> > >
> > > We are tokenizing usernames so that a username like "solr-user" will be
> > > tokenized into "solr" and "user", and will match both "sol" and "use"
> > > prefixes. The problem is when we get "solr-u" as a prefix, I'm having
> to
> > > split that up on the client side before I construct a query
> > "username:solr*
> > > username:u*". I'm basically using a regex as a poor man's tokenizer.
> > >
> > > Is there a better way to approach this? Is there a way to tell Solr to
> > > tokenize a string and use the parts as prefixes?
> > >
> > > - Hayden
> >
>
