Just for the records - this works like a charm:
.../select?q=*potter*&qt=dismax
−
0
93
−
*potter*
dismax
−
...
L'année où on a découvert «Harry Potter» au cinéma
...
explicit
0.01
all_text_de^0.5 all_text_en^0.5
solr-user@lucene.apache.org
> Sent: Thu, November 5, 2009 5:23:48 PM
> Subject: Re: leading and trailing wildcard query
>
> >
> > The guilt trick is not the best thing to try on public mailing lists. :)
> >
>
> Point taken, although not my intention. I guess I ha
7;ve scoured the archives and JIRA , but the answer to my question is just
not clear to me.
With all the new Solr 1.4 features, is there any way to do a leading and
trailing wildcard query on an *untokenized* field?
e.g. q=myfield:*abc* would return a doc with myfield=xxxabcxxx
Yes, I know how
> Not sure what version it was supported from, but we're on 1.3.
Really!? Great answer!
Thanks!
--
A. Steven Anderson
Not sure what version it was supported from, but we're on 1.3.
bern
-Original Message-
From: A. Steven Anderson [mailto:a.steven.ander...@gmail.com]
Sent: Friday, 6 November 2009 10:25 AM
To: solr-user@lucene.apache.org
Subject: Re: leading and trailing wildcard query
> Hi
> Note that N-grams are limited to specific string lengths. I presume that
> you need to search for arbitrary strings, not just three-letter ones.
>
Understood, but that is a limitation that we can live with.
Thanks!
--
A. Steven Anderson
> Ah. With that restriction, it is impossible.
> If it is OK to pay Lucid to make a one-line change, you might be able to do
> it. Otherwise, get ready to spend a lot of money for a search engine.
>
Well, now that Lucid is getting In-Q-Tel $$$, they will soon learn that
officially releases are all
@lucene.apache.org
Subject: Re: leading and trailing wildcard query
Thanks for the solution, but could you elaborate on how it would find
something like *abc* in a field that contains abc.
Steve
On Thu, Nov 5, 2009 at 5:25 PM, Bernadette Houghton <
bernadette.hough...@deakin.edu.au>
> Hi Steve, a query such as *abc* would need the NGramFilterFactor, hence the
> doubleedgytext, and would be retrievable by a query such as contains:abc.
> Note that you can set the max and minimum size of strings that get indexed.
>
Excellent! Just to clarify though, NGramFilterFactor is a Solr
Ah. With that restriction, it is impossible.
If it is OK to pay Lucid to make a one-line change, you might be able
to do it. Otherwise, get ready to spend a lot of money for a search
engine.
wunder
On Nov 5, 2009, at 3:18 PM, A. Steven Anderson wrote:
Unfortunately, we can only use offici
[mailto:a.steven.ander...@gmail.com]
Sent: Friday, 6 November 2009 10:08 AM
To: solr-user@lucene.apache.org
Subject: Re: leading and trailing wildcard query
Thanks for the solution, but could you elaborate on how it would find
something like *abc* in a field that contains abc.
Steve
On Thu, Nov 5
> Doesn't it work to call SolrQueryParser.setAllowLeadingWildcard?
Good question. Anyone?
> It can be really slow, what an RDBMS person would call a full table scan.
Understood.
> There is an open bug to make that settable in a config file, but this is a
> pretty tiny change to the source.
Because that is the semantics of Solr/Lucene wildcard syntax. * stands for
"any number of any character". Basically, it enumerates all the terms in the
field for all the documents and assembles a list of all of them that contain
the
substring "abc" and uses that as one of the clauses of your search
Thanks for the solution, but could you elaborate on how it would find
something like *abc* in a field that contains abc.
Steve
On Thu, Nov 5, 2009 at 5:25 PM, Bernadette Houghton <
bernadette.hough...@deakin.edu.au> wrote:
> I've just set up something similar (much thanks to Avesh!)-
>
>
e.org
Sent: Thu, November 5, 2009 3:04:32 PM
Subject: Re: leading and trailing wildcard query
No thoughts on this? Really!?
I would hate to admit to my Oracle DBE that Solr can't be
customized to do a
common query that a relational database can do. :-(
On Wed, Nov 4, 2009 at 6:01 PM, A.
2009 9:13 AM
To: solr-user@lucene.apache.org
Subject: Re: leading and trailing wildcard query
The guilt trick is not the best thing to try on public mailing lists. :)
The first thing that popped to my mind is to use 2 fields, where the second one
contains the desrever string of the first one
>
> The guilt trick is not the best thing to try on public mailing lists. :)
>
Point taken, although not my intention. I guess I have been spoiled by
quick replies and was getting to think it was a stupid question.
Plus, I'm literally gonna get trash talk from my Oracle DBE if I can't make
this
> a.steven.ander...@gmail.com> wrote:
>
> > I've scoured the archives and JIRA , but the answer to my question is just
> > not clear to me.
> >
> > With all the new Solr 1.4 features, is there any way to do a leading and
> > trailing wildcard query on a
and JIRA , but the answer to my question is just
> not clear to me.
>
> With all the new Solr 1.4 features, is there any way to do a leading and
> trailing wildcard query on an *untokenized* field?
>
> e.g. q=myfield:*abc* would return a doc with myfield=xxxabcxxx
>
> Yes,
I've scoured the archives and JIRA , but the answer to my question is just
not clear to me.
With all the new Solr 1.4 features, is there any way to do a leading and
trailing wildcard query on an *untokenized* field?
e.g. q=myfield:*abc* would return a doc with myfield=xxxabcxxx
Yes, I kno
20 matches
Mail list logo
