tool) you can view how your wildcard
query is re-written into boolean queries. This should help to catch
those cases where wildcard queries match unwanted terms.
--
Best regards,
Andrzej Bialecki
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retr
Luke Shannon wrote:
Hi Tod;
Thanks for your help.
I was able to do what you said but in a much uglier way using a Boolean
Query and adding Wildcard Queries.
The end result looks like this:
The query: +(type:138) +((-name:*tim* -name:*bill* -name:*harry*
+olfaithfull:stillhere))
But this one works
Hi Tod;
Thanks for your help.
I was able to do what you said but in a much uglier way using a Boolean
Query and adding Wildcard Queries.
The end result looks like this:
The query: +(type:138) +((-name:*tim* -name:*bill* -name:*harry*
+olfaithfull:stillhere))
But this one works as expected
Luke Shannon wrote:
The API I'm working with combines a series of queries into one larger one
using a boolean query.
Queries on the same field get OR's into one big query. All remaining queries
are AND'd with this big one.
Working with in this system I have:
arg = (mario luigi bo
The API I'm working with combines a series of queries into one larger one
using a boolean query.
Queries on the same field get OR's into one big query. All remaining queries
are AND'd with this big one.
Working with in this system I have:
arg = (mario luigi bobby joe) //i do have
1 PM
Subject: Re: Optional Terms in a single query
> On Monday 21 February 2005 23:23, Luke Shannon wrote:
> > Hi;
> >
> > I'm trying to create a query that look for a field containing type:181
and
> > name doesn't contain tim, bill or harry.
>
> typ
Luke Shannon wrote:
Hi;
I'm trying to create a query that look for a field containing type:181 and
name doesn't contain tim, bill or harry.
+(type: 181) +((-name: tim -name:bill -name:harry +oldfaith:stillHere))
+(type: 181) +((-name: tim OR bill OR harry +oldfaith:stillHere))
+
On Monday 21 February 2005 23:23, Luke Shannon wrote:
> Hi;
>
> I'm trying to create a query that look for a field containing type:181 and
> name doesn't contain tim, bill or harry.
type: 181 -(name: tim name:bill name:harry)
> +(type: 181) +((-name: t
Hi;
I'm trying to create a query that look for a field containing type:181 and
name doesn't contain tim, bill or harry.
+(type: 181) +((-name: tim -name:bill -name:harry +oldfaith:stillHere))
+(type: 181) +((-name: tim OR bill OR harry +oldfaith:stillHere))
+(type: 181) +((-name:*(tim
quot;c" is cheaper than testing for "(a OR
> >b)" and I rewrote the query as:
> >c AND (a OR b)
> >Would the query run faster?
> >
> >Sorry if this has already be answered, but for some reason the Archive
> >search is not working for me today.
> >
Runde, Kevin wrote:
Hi All,
How does Lucene handle multi term queries? Does it use short circuiting?
So if a user entered:
(a OR b) AND c
But my program knew testing for "c" is cheaper than testing for "(a OR
b)" and I rewrote the query as:
c AND (a OR b)
Would the query run f
On Monday 21 February 2005 19:59, Runde, Kevin wrote:
> Hi All,
>
> How does Lucene handle multi term queries? Does it use short circuiting?
> So if a user entered:
> (a OR b) AND c
> But my program knew testing for "c" is cheaper than testing for "(a OR
> b)&
Hi All,
How does Lucene handle multi term queries? Does it use short circuiting?
So if a user entered:
(a OR b) AND c
But my program knew testing for "c" is cheaper than testing for "(a OR
b)" and I rewrote the query as:
c AND (a OR b)
Would the query run faster?
Sorry if
Thank you this helped a lot...
Michael Celona
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Monday, February 21, 2005 11:55 AM
To: Lucene Users List
Subject: Re: Using the highlighter from the sandbox with a prefix query.
On Feb 21, 2005, at 10:53 AM
>One thing to mention
> that I am using a
> MultiSearcher to rewrite the queries. I tried...
Ah. I remember this got a little ugly. The highlighter
has a Junit test that demonstrates highlighting fuzzy
queries when using a multisearcher. Take a look at
that.
I can't remember the ins and outs of t
On Feb 21, 2005, at 10:53 AM, Michael Celona wrote:
That the only stack I get. One thing to mention that I am using a
MultiSearcher to rewrite the queries. I tried...
query = searcher_last.rewrite( query );
query = searcher_cur.rewrite( query );
using IndexSearcher and I don't get an
That the only stack I get. One thing to mention that I am using a
MultiSearcher to rewrite the queries. I tried...
query = searcher_last.rewrite( query );
query = searcher_cur.rewrite( query );
using IndexSearcher and I don't get an error... However, I not able to
highlight wildcard qu
On Feb 21, 2005, at 10:20 AM, Michael Celona wrote:
I am using
query = searcher.rewrite( query );
and it is throwing java.lang.UnsupportedOperationException .
Am I able to use the searcher rewrite method like this?
What's the full stack trace?
I am using
query = searcher.rewrite( query );
and it is throwing java.lang.UnsupportedOperationException .
Am I able to use the searcher rewrite method like this?
Thanks,
Michael
-Original Message-
From: Daniel Naber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 17, 2005
Thanks Erik. Option 2 sounds like the path of least resistance.
Luke
- Original Message -
From: "Erik Hatcher" <[EMAIL PROTECTED]>
To: "Lucene Users List"
Sent: Thursday, February 17, 2005 9:05 PM
Subject: Re: Query Question
> On Feb 17, 2005, at 5:51 P
n't too large, cached filters might be another
alternative.
Of couse the filter would have to be recreated whenever the index changes.
The advantage is, that you save searching for the types for each query
where the filter
alize this?
What's wrong with that method? I don't think you can do it any simpler.
Are you concerned about writing a string then having to use the query
parser? You could also build it up manually:
QueryParser parser = ...
Query text = parser.parse(queryText);
Query type = new Boo
Hi,
i've problem with my my classes using lucene.
my index looks like:
type | content
-
document | x
document | x
view | x
view | x
dbentry| x
dbentry| x
my question now:
how can i search for content where typ
On Feb 17, 2005, at 5:51 PM, Luke Shannon wrote:
My manager is now totally stuck about being able to query data with *
in it.
He's gonna have to wait a bit longer, you've got a slightly tricky
situation on your hands
WildcardQuery(new Term("name", "*home\**&
Hello;
My manager is now totally stuck about being able to query data with * in it.
Here are two queries.
TermQuery(new Term("type", "203"));
WildcardQuery(new Term("name", "*home\**"));
They are joined in a boolean query. That query gives this result w
That is a query toString(). I created the Query using a Wildcard Query
object.
Luke
- Original Message -
From: "Erik Hatcher" <[EMAIL PROTECTED]>
To: "Lucene Users List"
Sent: Thursday, February 17, 2005 3:00 PM
Subject: Re: Query Question
>
> O
On Feb 17, 2005, at 2:44 PM, Luke Shannon wrote:
Hello;
Why won't this query find the document below?
Query:
+(type:203) +(name:*home\**)
Is that what the query toString is? Or is that what you handed to
QueryParser?
Depending on your analyzer, 203 may go away. QueryParser doesn'
Hello;
Why won't this query find the document below?
Query:
+(type:203) +(name:*home\**)
Document (relevant fields):
Keyword
Keyword
I was hoping by escaping the * it would be treated as a string. What am I
doing wrong?
Thanks,
Thanks very much Marc and Daniel. That solved the problem!!
On Thu, 2005-02-17 at 08:55 +, mark harwood wrote:
> See the highlighter's package.html for a description
> of how query.rewrite should be used to solve this.
>
> Cheers,
> Mark
>
On Thursday 17 February 2005 08:37, lucuser4851 wrote:
> We have been using the highlighter from the lucene sandbox, which works
> very nicely most of the time. However when we try and use it with a
> prefix query (which is what you get having parsed a wild-card query), it
> doesn&
the time. However when we try
> and use it with a
> prefix query (which is what you get having parsed a
> wild-card query), it
> doesn't return any highlighted sections. Has anyone
> else experienced
> this problem, or found a way aro
Dear All,
We have been using the highlighter from the lucene sandbox, which works
very nicely most of the time. However when we try and use it with a
prefix query (which is what you get having parsed a wild-card query), it
doesn't return any highlighted sections. Has anyone else experienced
arser.ParseException: Encountered "is" at
line 1, column 15.
Was expecting:
"]" ...
when I tried to parse the following string "[this is a test]".
I can't find any documentation that tells me what the brackets do to
a query. I had a user that was used to anoth
"]" ...
when I tried to parse the following string "[this is a test]".
I can't find any documentation that tells me what the brackets do to a
query. I had a user that was used to another search engine that used
[] to do proximity or near searches and tried it on this
Hi,
lucene.apache.org seems to work now.
Here is the query syntax:
http://lucene.apache.org/queryparsersyntax.html
[] is used as [BEGIN-RANGE-STRING TO END-RANGE-STRING]
Otis
--- Jim Lynch <[EMAIL PROTECTED]> wrote:
> First I'm getting a
>
>
> The requested URL
lowing string "[this is a test]".
I can't find any documentation that tells me what the brackets do to a
query. I had a user that was used to another search engine that used []
to do proximity or near searches and tried it on this one. Actually I'd
like to see the documentation
That worked. Thanks a lot.
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Monday, February 07, 2005 11:39 AM
To: Lucene Users List
Subject: Re: Query Analyzer
On Feb 7, 2005, at 11:29 AM, Ravi wrote:
> How do I set the analyzer when I build the query in my c
On Feb 7, 2005, at 11:29 AM, Ravi wrote:
How do I set the analyzer when I build the query in my code instead of
using a query parser ?
You don't. All terms you use for any Query subclasses you instantiate
must match exactly the terms in the index. If you need an analyzer to
do this then y
How do I set the analyzer when I build the query in my code instead of
using a query parser ?
Thanks in advance
Ravi.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
g I check to make sure there
is a "kcfileupload" field.
This is not a good solution, and I hope to replace it soon. If anyone has
ideas please let me know.
Luke
- Original Message -
From: "Chris Hostetter" <[EMAIL PROTECTED]>
To: "Lucene Users List"
S
r" <[EMAIL PROTECTED]>
To: "Lucene Users List"
Sent: Friday, February 04, 2005 3:03 PM
Subject: Re: Parsing The Query: Every document that doesn't have a field
containing x
Another approach...
You can make a Filter that is the inverse of the output from another
filter, which
I have been playing with the test below.
The problem I have is this line:
Query query2 = QueryParser.parse("*", "kcfileupload", new
StandardAnalyzer());
Results in the following error:
org.apache.lucene.queryParser.ParseException: Lexical error at line 1,
column 2. E
Another approach...
You can make a Filter that is the inverse of the output from another
filter, which means you can make a QueryFilter on the search, then wrap it
in your inverse Filter.
you can't execute a query on a filter without having a Query object, but
you can just apply the F
Very Nice. Thanks!
Luke
- Original Message -
From: "åç" <[EMAIL PROTECTED]>
To: "Lucene Users List"
Sent: Friday, February 04, 2005 2:12 AM
Subject: Re: Parsing The Query: Every document that doesn't have a field
containing x
I think you may can use a
ke to look at your index.
>
> Otis
>
>
> --- Hetan Shah <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > How can one search for a document based on the query which has
> > numbers
> > in the query srting.
> >
> > e.g. query = Java 2
document.add(Field.Text("keywords", "jakes sensitive info"));
writer.addDocument(document);
writer.close();
}
public void testSecurityFilter() throws Exception {
TermQuery query = new TermQuery(new Term("keywords", "info")
Bingo! Nice catch. That was it. Made everything lower case when I set the
field. Works great now.
Thanks!
Luke
- Original Message -
From: "Kauler, Leto S" <[EMAIL PROTECTED]>
To: "Lucene Users List"
Sent: Thursday, February 03, 2005 6:48 PM
Subject: RE
Because you are build from QueryParser rather than a TermQuery, all
search terms in the query are being lowercased by StandardAnalyzer.
So your query of "olFaithFull:stillhere" requires that there is an exact
index term of "stillhere" in that field. It depends on how you bu
"stillHere"
Capital H.
- Original Message -
From: "Kauler, Leto S" <[EMAIL PROTECTED]>
To: "Lucene Users List"
Sent: Thursday, February 03, 2005 6:40 PM
Subject: RE: Parsing The Query: Every document that doesn't have a field
containi
ueryParser.parse("stillHere",
> "olFaithFull", new StandardAnalyzer());
> BooleanQuery typeNegativeSearch = new BooleanQuery();
> typeNegativeSearch.add(query1, true, false);
> typeNegativeSearch.add(query2, true, false);
>
&
arser.parse("stillHere", "olFaithFull", new
StandardAnalyzer());
BooleanQuery typeNegativeSearch = new BooleanQuery();
typeNegativeSearch.add(query1, true, false);
typeNegativeSearch.add(query2, true, false);
Reutrns 0 results and is in string form : +kcfileupload:jpg
nt based on the query which has
> numbers
> in the query srting.
>
> e.g. query = Java 2 Platform J2EE
>
> What do I need to do so that the numbers do not get neglected.
>
> I am using StandardAnalyzer to index the pages and using StopAnalyzer
> to
> search
Hetan Shah wrote:
Hello,
How can one search for a document based on the query which has numbers
in the query srting.
e.g. query = Java 2 Platform J2EE
What do I need to do so that the numbers do not get neglected.
I am using StandardAnalyzer to index the pages and using StopAnalyzer to
search
Hello,
How can one search for a document based on the query which has numbers
in the query srting.
e.g. query = Java 2 Platform J2EE
What do I need to do so that the numbers do not get neglected.
I am using StandardAnalyzer to index the pages and using StopAnalyzer to
search the documents
I did, I have ran both queries in Luke.
kcfileupload:ppt
returns 1
olFaithfull:stillhere
returns 119
Luke
- Original Message -
From: "Maik Schreiber" <[EMAIL PROTECTED]>
To: "Lucene Users List"
Sent: Thursday, February 03, 2005 4:55 PM
Subject: Re: Parsing
Yes. There should be 119 with stillHere,
You have double-checked that, haven't you? :)
and if I run a query in Luke on
kcfileupload = ppt, it returns one result. I am thinking I should at least
get this result back with: -kcfileupload:jpg +olFaithFull:stillhere?
You really should.
--
Yes. There should be 119 with stillHere, and if I run a query in Luke on
kcfileupload = ppt, it returns one result. I am thinking I should at least
get this result back with: -kcfileupload:jpg +olFaithFull:stillhere?
Luke
- Original Message -
From: "Maik Schreiber" <[EM
-kcfileupload:jpg +olFaithFull:stillhere
This looks right to me. Why the 0 results?
Looks good to me, too. You sure all your documents have
olFaithFull:stillhere and there is at least a document with kcfileupload not
being "jpg"?
--
Maik Schreiber * http://www.blizzy.de <-- Get GMail invites
Hello,
Still working on the same query, here is the code I am currently working
with.
I am thinking this should bring up all the documents that have
olFaithFull=stillHere and kcfileupload!=jpg (so anything else)
query1 = QueryParser.parse("jpg", "kcfileupload", new Standar
Ok.
I have added the following to every document:
doc.add(Field.UnIndexed("olFaithfull", "stillHere"));
The plan is a query that says: olFaithull = stillHere and kcfileupload!=jpg.
I have been experimenting with the MultiFieldQueryParser, this is not
working out for me.
one nonnegated
>> term to return documents; in other words, it isn't possible to
>> use a query like NOT term to find all documents that don't
>> contain a term.
>>
>> So does that mean the above example wouldn't work?
>>
> Exactly. You can
Negating a term must be combined with at least one nonnegated term to return
documents; in other words, it isn't possible to use a query like NOT term to
find all documents that don't contain a term.
So does that mean the above example wouldn't work?
Exactly. You ca
Hello;
I have a query that finds document that contain fields with a specific
value.
query1 = QueryParser.parse("jpg", "kcfileupload", new StandardAnalyzer());
This works well.
I would like a query that find documents containing all kcfileupload fields
that don't co
How are you indexing your document?
If you're using QueryParser with the default operator set to OR (which
is the default), then you've already provided the expression you need
:)
Erik
On Feb 1, 2005, at 6:29 PM, Hetan Shah wrote:
Hello All,
What should my query look like if
Hello All,
What should my query look like if I want to search all or any of the
following key words.
Sun Linux Red Hat Advance Server
replies are much appreciated.
-H
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
This from the highlighter package will give you the IDF :
WeightedTerm[] QueryTermExtractor.getIdfWeightedTerms(Query query,
IndexReader reader, String fieldName)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
I implemented a Query version of the TermVector
org.apache.lucene.search.QueryTermVector
Works off of an array of Strings or a String and an Analyzer. Is this
what you are looking for?
>>> [EMAIL PROTECTED] 1/28/2005 6:33:18 AM >>>
On Jan 27, 2005, at 10:24 PM, Jonathan Lask
cene,
then translate the Lucene results into meaningful links. It actually
works
better than it sounds, however it could be easier.
If I could just give Lucene a query result (i.e. a list of rows) and
then
have Lucene send me back say the primary key of the rows that match
and the
other Lucen
Lucene a query result (i.e. a list of rows) and then
have Lucene send me back say the primary key of the rows that match and the
other Lucene goodness: ranking, number of hits, etc.
Could be pretty powerful and simplify the deployment for database driven
applications.
[Note: this opinion and
. For example,
sorting on the date field, and any other range query.
I think the better way is to look at ways to integrate lucene tightly
into a java relational database, such as HSQL, McKoi or Derby.
In particular, that integration would make it possible for queries
like "contains(...)"
had similar success with Derby (Cloudscape).
This approach has some appeal and I've been able to
use the same class as a UDF in both databases but it
does have issues: it looks like this UDF based
integration won't scale. The above query took 80
milliseconds using 10,000 records. Anoth
> I'm not sure why you choose that.
I just thought that Query Parser needs to be specifies what it should
expect before hand. So did "field AND field". But I was wrong.
> Further name:\"john\" and name:john should be the same.
Just in case it's not "john&quo
sunil goyal writes:
>
> I was just trying that...
>
> QueryParser qp = new QueryParser("field AND field", new StandardAnalyzer());
> Query query = qp.parse("name:\"john\" AND age:[10 TO 16]");
>
> It works fine with this. Do I need to speci
I've merged some different fields in one query, with the name of one of
these fields as the second parameter in the
static method, and it worked fine.
Also, you can do a little query parser, and build the queries with
BooleanQuery.
David
sunil goyal wrote:
Hello,
I was just trying
Hello,
I was just trying that...
QueryParser qp = new QueryParser("field AND field", new StandardAnalyzer());
Query query = qp.parse("name:\"john\" AND age:[10 TO 16]");
It works fine with this. Do I need to specify that QueryParser should
expect things in order
Hello,
To build queries, you can generate a query like "(text:house OR
text:car) AND (keywords:building)", and then
parse it with the QueryParser.parse method to get the Lucene query.
Is not 100% sql-like syntax, but it's more clear
than the lucene syntax.
Hope it he
On Jan 28, 2005, at 12:40, sunil goyal wrote:
I want to run dynamic queries against the lucene index. Is there any
native syntax available for Lucene so that I can query, by first
generating the query in say an XML or SQL like format (cache this
query) and then use this query over lucene index
Hello all,
I want to run dynamic queries against the lucene index. Is there any
native syntax available for Lucene so that I can query, by first
generating the query in say an XML or SQL like format (cache this
query) and then use this query over lucene index.
e.g. So a lucene query syntax in
On Jan 27, 2005, at 10:24 PM, Jonathan Lasko wrote:
No, the number of occurrences of a term in a Query.
Nothing built-in gives you this. You'd have to dissect the Query
clause-by-clause and cast each clause to the proper type to pull the
terms from them. The Highlighter code does this
No, the number of occurrences of a term in a Query.
Jonathan
Quoting David Spencer <[EMAIL PROTECTED]>:
> Jonathan Lasko wrote:
>
> > What do I call to get the term frequencies for terms in the Query? I
> > can't seem to find it in the Javadoc...
>
> Do
Jonathan Lasko wrote:
What do I call to get the term frequencies for terms in the Query? I
can't seem to find it in the Javadoc...
Do you mean the # of docs that have a term?
http://jakarta.apache.org/lucene/docs/api/org/apache/lucene/index/IndexReader.html#docFreq(org.apache.lucene.index
What do I call to get the term frequencies for terms in the Query? I
can't seem to find it in the Javadoc...
Thanks.
Jonathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
"synonyms" (thus easier to use) or make
it separate (too academic?)
Well... the ideal case would be (easy) customization :-), form an
external text (XML ?) file. Depending of the kind of relationship, the
boost factor could be adjusted when the query is expanded. The same on
relationships&#
Pierrick Brihaye wrote:
Hi,
David Spencer a écrit :
One example of expansion with the synonym boost set to 0.9 is the
query "big dog" expands to:
Interesting.
Do you plan to add expansion on other Wordnet relationships ? Hypernyms
and hyponyms would be a good start point for thes
Hi,
David Spencer a écrit :
One example of expansion with the synonym boost set to 0.9 is the query
"big dog" expands to:
Interesting.
Do you plan to add expansion on other Wordnet relationships ? Hypernyms
and hyponyms would be a good start point for thesaurus-like search,
w
Based on mail from Doug I wrote a "more like this" query generator,
named, well, MoreLikeThis. Bruce Ritchie and Mark Harwood made changes
to it (esp term vector support) and bug fixes. Thanks to everyone.
I've checked in the code to the sandbox under contributions/similarity.
Um.. Nevermind.. I figured it out.. I was using the StandardAnalyzer
when I built my index and thus didn't have N or St in the index itself.
R
-Original Message-
From: Ryan Aslett
Sent: Friday, January 14, 2005 11:18 AM
To: Lucene Users List
Subject: Boolean Query
Okay, I
Okay, Im not grokking something here. Im trying to run a query that
returns only the results that have *all* of the terms in my query
string.
When I run this query, which I construct myself and do a
Analyzer analyzer = new WhitespaceAnalyzer();
QueryParser qp = new QueryParser("ad
in WordNet, it could probably
> be used to ignore the uncommon meanings.
If you just go search CiteSeer for "WordNet", you will find the output
of every failed MS thesis experiment to improve retrieval performance
by naive applic
On Wednesday 12 January 2005 01:47, David Spencer wrote:
> Amusingly then, documents with the terms "liberal wienerwurst" match
> "big dog"! :)
There's something like frequency information in WordNet, it could probably
be used to ignore the uncommon meanings.
Regards
Daniel
--
http://www.dan
#x27;s no need to upgrade WordNet for this package at least.
I added "query expansion" which takes in a simple query string and for
every term adds their synonyms. There's an optional boost parameter to
be used to "penalize" synonyms if you want to use the heuristic that the
u
Jim Lynch wrote:
From what I've read, if you want to have a choice, the easiest way is
to index the documents twice. Once with stemming on and once with it off
placing the results in two different indexes. Then at query time,
select which index you want to use based on whether you
: >Is it possible to enable stem queries on a per-query basis? It doesn't
: >seem to be possible since the stem tokenizing is done during the
: >indexing process. Are people basically stuck with having all their
: >queries stemmed or none at all?
: From what I've read,
From what I've read, if you want to have a choice, the easiest way is
to index the documents twice. Once with stemming on and once with it off
placing the results in two different indexes. Then at query time,
select which index you want to use based on whether you want stemming on
o
Hi,
I'm new to Lucene, so I apologize if this issue has been discussed
before (I'm sure it has), but I had a hard time finding an answer using
google. (Maybe this would be a good candidate for the FAQ!) :)
Is it possible to enable stem queries on a per-query basis? It doesn't
seem
Sorry for the duplicate on lucene-dev, it should have gone to lucene-user
directly:
A bit more:
On Thursday 06 January 2005 10:22, Paul Elschot wrote:
> On Thursday 06 January 2005 02:17, Andrew Cunningham wrote:
> > Hi all,
> >
> > I'm currently doing a quer
On Thursday 06 January 2005 02:17, Andrew Cunningham wrote:
> Hi all,
>
> I'm currently doing a query similar to the following:
>
> for w in wordset:
> query = w near (word1 V word2 V word3 ... V word1422);
> perform query
>
> and I am doing this through
Hi all,
I'm currently doing a query similar to the following:
for w in wordset:
query = w near (word1 V word2 V word3 ... V word1422);
perform query
and I am doing this through SpanQuery.getSpans(), iterating through the
spans and counting
the matches, which can result in 4782282 ma
On Dec 27, 2004, at 6:28 AM, Alex Kiselevski wrote:
Thanks Erik,
I use StandardAnalyze to index RPG/4.
I use StandardAnalyzer and IndexSearcher with TermQuery without
QueryParser. So, I thought that as a result of query
Text:RPG I still have to get some hit, but it didn't h
Thanks Erik,
I use StandardAnalyze to index RPG/4.
I use StandardAnalyzer and IndexSearcher with TermQuery without
QueryParser. So, I thought that as a result of query
Text:RPG I still have to get some hit, but it didn't happen.
-Original Message-
From: Erik Hatcher [mailto:[
1 - 100 of 718 matches
Mail list logo
