Thanks for the link.
I had overlooked the fact that RangeQuery expands to a sequence of term
queries and throws an exception when 1024 is reached.
By setting the BooleanQuery.setMaxClauseCount() to the required value, I was
able to avoid the TooManyClauses exception. But, as mentioned in the FAQ
> +entity:product +(name:"audio cable"^2.0 content:"audio cable")
Looks good to me. This query would only return products where either name or
content matches "audio cable" (or both), and name matches get a higher score.
> Also I saw that
> my OR gets represented as a blank in the query. Is that
Hi,
After a little probing and trying I formulated this query:
queryString = "entity:\"" + en + "\" AND (name:\"" + queryString + "\"^2
OR content:\"" + queryString + "\")";
Query q = QueryParser.parse(queryString, "content", analyzer);
When I execute the above query, the fol
Any reason why Range query doesn't just iterate over the terms of the
field instead of creating a large BooleanQuery with term queries?
Are there any specific difficultites in doing so or any other impacts?
Thanks
-John
On 5/19/05, Jayakumar.V <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm getting a
: I'm in need of a special version of the phrase query. For example, given a
: search phrase "alpha beta gamma", I'ld like a to score documents something
like
: the following manner.
it sounds like what you want isn't really a special type of query, it's a
special type of query parser.
all of ht
Hi all, its me again.
I'm in need of a special version of the phrase query. For example, given a
search phrase "alpha beta gamma", I'ld like a to score documents something like
the following manner.
If document contains exactly "alpha beta gamma", score = 1
If document contains "alpha gamma beta"
On Friday 20 May 2005 17:20, Terry Steichen wrote:
> Paul,
>
> Could you flesh out the implementation you describe below with some code
> or pseudocode?
You can start from this:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34331
and use code from the method in src/java
org.surround.search.S
On Friday 20 May 2005 16:21, Robert Newson wrote:
> Paul Elschot wrote:
> > On Friday 20 May 2005 13:58, Max Pfingsthorn wrote:
> >
> >>Hi!
> >>
> >>I was wondering if Lucene has any sort of functionality to distribute
> >
> > indices so that different fields are stored in separate indices but t
Paul,
Could you flesh out the implementation you describe below with some code
or pseudocode?
Regards,
Terry
Paul Elschot wrote:
On Friday 20 May 2005 11:30, Stanislav Jordanov wrote:
Is there a Lucene Query (or something that will do a job) like:
"Star Wars tri*"
that will match all docs cont
Paul Elschot wrote:
On Friday 20 May 2005 13:58, Max Pfingsthorn wrote:
Hi!
I was wondering if Lucene has any sort of functionality to distribute
indices so that different fields are stored in separate indices but they
still refer to the same document. This would be great for a situation where
t
On Friday 20 May 2005 13:58, Max Pfingsthorn wrote:
> Hi!
>
> I was wondering if Lucene has any sort of functionality to distribute
indices so that different fields are stored in separate indices but they
still refer to the same document. This would be great for a situation where
there are many
Hi!
I was wondering if Lucene has any sort of functionality to distribute indices
so that different fields are stored in separate indices but they still refer to
the same document. This would be great for a situation where there are many
large documents which have frequently changing properties
On Friday 20 May 2005 11:30, Stanislav Jordanov wrote:
> Is there a Lucene Query (or something that will do a job) like:
> "Star Wars tri*"
>
> that will match all docs containing a 3 word phrase: 'Star' followed by
> 'Wars' followed by a word starting with 'tri'.
>
> I.e. the above query will m
Is there a Lucene Query (or something that will do a job) like:
"Star Wars tri*"
that will match all docs containing a 3 word phrase: 'Star' followed by
'Wars' followed by a word starting with 'tri'.
I.e. the above query will match both "Star Wars trilogy" and "Star Wars
triumph".
(I know about
On May 20, 2005, at 3:55 AM, Möckl Susanne wrote:
In my index are (for example) 4 documents which contains the word
simone.
The problem is that lucene does not find all documents by some inputs.
To explain here some examples and what they return:
input: simonereturns: 4 hits
Hi,
I´m using lucene for 2 month and now I have a big problem.
In my index are (for example) 4 documents which contains the word simone.
The problem is that lucene does not find all documents by some inputs.
To explain here some examples and what they return:
input: sim
: You're right!
: Unfortunately someone's name in my company is 'such' and you made me
: realize that it's also a common english word. It's in the
: StopAnalyzer.ENGLISH_STOP_WORDS.
: I'll try to handle that...
if you have a field that is used exclusively for names of people, you may
want to use a
> : When I search "hotliner:such" I get a 0 result. ("such" gets the same)
> : But when I search "hotliner:such*", I get the 277 expected results!
>
> (or treating it as a stop word)
You're right!
Unfortunately someone's name in my company is 'such' and you made me
realize that it's also a common
18 matches
Mail list logo
