See:
https://lucidworks.com/2011/11/29/whats-with-lowercasing-wildcard-multiterm-queries-in-solr/
It discusses the general problem of particular filters being able to
cope with wildcards or not. Generally any filter that could
potentially produce more than one output token per input token is
skip
You may want to use UAX29URLEmailTokenizerFactory tokenizer into your
analysis chain.
Thanks,
Susheel
On Thu, Sep 14, 2017 at 8:46 AM, Shawn Heisey wrote:
> On 9/14/2017 5:06 AM, Mannott, Birgit wrote:
> > I have a problem when searching on email addresses.
> > @ seems to be handled as a speci
On 9/14/2017 5:06 AM, Mannott, Birgit wrote:
> I have a problem when searching on email addresses.
> @ seems to be handled as a special character but I don't find anything about
> it in the documentation.
>
> This is my test data
> t...@one.com
> t...@two.com
Chances are that have analysis define
Hi,
Can you give us a little information about the query parser you using in
your handler ?
Thanks,
Ati
On Thu, Sep 14, 2017 at 4:36 PM, Mannott, Birgit
wrote:
> Hi,
>
> I have a problem when searching on email addresses.
> @ seems to be handled as a special character but I don't find anythin
Hi,
Thanks for the information. I would appreciate if somebody can share the URL
of the JIRA issue.
Otis Gospodnetic wrote:
>
>
> Prerna,
>
> Yes, DisMax doesn't take in queries with Boolean operators. But I believe
> there is a patch in JIRA that makes that possible.
>
> Otis
> --
> Semate
Prerna,
Yes, DisMax doesn't take in queries with Boolean operators. But I believe
there is a patch in JIRA that makes that possible.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: prerna07
> To: solr-user@lucene.apache.org
> Sent: Mond
