y overriding the factory method
> that creates range queries (I assume you are German and know this IT
> magazine).
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Origi
Hi all,
I'm searching for a way to reuse a Lucene search.
For example, I'm searching for the word "acci". But too many ScoreDocs are
returned, and I provide: "accide". Can it reuse the
existing search? Or is it just better to create a new and fresh Lucene
search?
Jochen
Hi all,
I have an application which holds a list of documents. These documents are
indexed using Lucene.
I can search on keywords of the documents. I loop the TopDocs and get the
ID field (of each Lucene doc) which is related to the ID column in my
relational database. From all these ID's, I creat
t;http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes>
> DBSight customer, a shopping comparison site, (anonymous per request) got
> 2.6 Million Euro funding!
>
>
> On 7/3/12 12:56 AM, Jochen Hebbrecht wrote:
>
>> Hi all,
>>
>> I have an application which
_Lucene_**Database_Search_in_3_minutes<
> http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes
> >
> > DBSight customer, a shopping comparison site, (anonymous per request) got
> > 2.6 Million Euro funding!
> >
> >
> > On 7/3/12 12:56 AM, Joch
dles.
>
> regards
>
> Torsten
>
> Am Montag, den 02.07.2012, 15:44 +0200 schrieb Jochen Hebbrecht:
> > Hi all,
> >
> > I currently have a Seam component which is in my session. This component
> is
> > holding (private attribute) a custom "Lucene object&quo
Thanks Ian, I'll give it a try!
2012/7/3 Ian Lea
> You can use the QueryParser proximity feature e.g. "foo test"~n where
> n is the max distance you want them to be apart. Or look at the
> SpanQuery stuff e.g. SpanNearQuery.
>
>
> --
> Ian.
>
>
quot;term 100 xxx"
> as well as "term 1" and "term 2". If your TEST values are that
> predictable you could split them up and index the number separately,
> maybe using NumericField and build a query using NumericRangeQuery.
>
> RegexQuery in contrib-queries
Hmm, just thinking. I could split the value on spaces.
Then I can say:
+TEST:Microsoft +TEST:[Belgium TO Spain]
I just tested it, and it seems to work :-) ...
2012/8/20 Jochen Hebbrecht
> Hi Ian,
>
> Thanks for your answer!
> Well, my example might have been not so clear. Her
s in Luke.
> >>
> >> Sounds very flaky anyway - you'd get "term 10 xxx" and "term 100 xxx"
> >> as well as "term 1" and "term 2". If your TEST values are that
> >> predictable you could split them up and index the numb
e, or as a wildcard or prefix query (e.g.,
>"Microsoft*"), or as a range query with the full literal string values.
>
>-- Jack Krupansky
>
>-Original Message-
>From: Jochen Hebbrecht
>Sent: Monday, August 20, 2012 9:13 AM
>To: java-user@lucene.apache.org
>Subject
Hi,
Imagine you are indexing the following documents (every line is stored in 1
single field, analyzed with the default StandardAnalyzer):
- Doc 1: restaurant 't Robbeke fish passoa beer 15 EUR 5 EUR 2 EUR total 22
EUR
- Doc 2: restaurant De Genieter scampi's fish sticks cola fanta 18 EUR 15
EUR 2
> containing SOME words in DOC4 may be listed too, but will get lower score.
>
>
> At 2012-09-07 15:32:23,"Jochen Hebbrecht"
> wrote:
> >Hi,
> >
> >Imagine you are indexing the following documents (every line is stored in
> 1
> >single field, analy
Thanks! Works like a charm :-)!
2012/9/7 Trejkaz
> On Fri, Sep 7, 2012 at 6:12 PM, Jochen Hebbrecht
> wrote:
> > Hi qibaoyuan,
> >
> > I tried your second solution, using the scoring data. I think in this
> way,
> > I could use MoreLikeThis. All document
will be passed directly to the analyzer, but the standard analyzer will
> in fact always remove it. Maybe you want the white space analyzer or
> keyword
> analyzer (no characters removed.)
>
> -- Jack Krupansky
>
> -Original Message- From: Jochen Hebbrecht
> Sen
alyzer.
>
> -- Jack Krupansky
>
> -Original Message- From: Jochen Hebbrecht
> Sent: Monday, October 01, 2012 10:34 AM
> To: java-user@lucene.apache.org
> Subject: Re: Searching for a search string containing a literal slash
> doesn't work with QueryParser
>
&
16 matches
Mail list logo