Hi ALL,
First thnx for spending time to read the message.
Am using MatchAllDocsQuery to get all the documents .
But i need documents that are unique based on keyword .
in my document keyword feild had values like 1,2,2,3,4,5,5,5,5 so on.
so the result i need is only 1,2,3,4,5 so on ...
Hi,
I followed the following procedure to escape special characteres.
String escapedKeywords = QueryParser.escape(keywords);
Query query = new QueryParser(content, new
StandardAnalyzer()).parse(escapedKeywords);
this works with most of the special characters like * and ~ except \ . I
can't do a
Hello to all,
Thanks for help in advance.
Example docs:
1,car, volvo, dealer, tyres
2,car, mercedes, dealer, tyres
3,car, renault, export, tyres
So, if i look for car, so i would like to get, except normal
results, a list of most frequent terms in result set.
This would be in my example:
Look into adding Term Vectors to your fields, which will store the
term frequency by document. Then you can use the TermVectorMapper to
load them sorted by frequency across all the documents in your set.
-Grant
On Aug 4, 2008, at 7:40 AM, Martin vWysiecki wrote:
Hello to all,
Thanks
I have a search which needs to find dates which are specified in two
different fields.
For an example:
I have a Java object with a date field that starts the time something
started and another that specifies the time that something ended.
I need to do a date search that the range is specified
Ok, say each line is an address. So the text file would look like:
123 Water St. Somerville, GA 12345
456 Easy St. Hope, CA 45676
34 Ocean Blvd. Staten Island, NY 93843
The file would have hundreds of thousands of addresses.
So the user would type 34, St in the search box and press a Search
Could you explain your problem a bit more? It's completely unclear
to me what java objects have to do with searching a lucene index.
If you're extracting data from some java objects somewhere to
insert in an index, then it's up to you to index them such that you
can extract the information in a
Thanks for the feedback and the quick response. The problem was a result of
unclear requirements fortunately I do not have to specify the range to be
between two different fields.
Erick Erickson wrote:
Could you explain your problem a bit more? It's completely unclear
to me what java
hello,
is there any date for the 2.3.3 release?
best,
-C.B.
Alas, not yet -- at least it hasn't been discussed yet.
Mike
Cam Bazz wrote:
hello,
is there any date for the 2.3.3 release?
best,
-C.B.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
I am still in trouble deleting documents.
Appearently - when an indexwriter and searcher is open at the same directory
- you can not delete documents with ids.
to delete documents with ids you need to access indexreader which is only
accessible tru the indexsearcher, thus resulting in a lock
Cam Bazz wrote:
I am still in trouble deleting documents.
OK but 2.3.3 isn't going to help you here -- it doesn't change
anything about deletion of docs.
Appearently - when an indexwriter and searcher is open at the same
directory
- you can not delete documents with ids.
If you need
yes, thats why I asked any news for release of 2.3.3.
I will be using it in a production environment and a little paranoid about
using the trunk.
I have been waiting for this delete by query for a long time.
Best,
-C.B.
On Tue, Aug 5, 2008 at 3:45 AM, Michael McCandless
[EMAIL PROTECTED]
Hi,
The indexer can't be opened after about 20 queries in linux system, but it is
fine if the index is in windows system. The indexer is the same in both
systems.
reader = IndexReader.open(indexName); //failed after about 20
queries
searcher = new IndexSearcher(reader);
Xh,
We need to see a little more code her. Are you reopening the reader for each
query? If so are you closing it each time?
We need more information.
John G.
-Original Message-
From: xh sun [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2008 8:34 PM
To:
Xh,
Sorry about those questions. I received two copies of your email. The first
was corrupt.
We still need to see more code. No there isn't any special config necessary.
John G.
-Original Message-
From: xh sun [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2008 8:34 PM
To:
As in the subject title, it seems the word 'not' is being excluded from my
searches. Note the lowercase, it isn't being treated as the boolean operator
'NOT'. For example, given the query sticks not stones, it parses it as
+keywords:stick +keywords:stone. Whereas if I use the query sticks NOT
Hi,
I guess it is with your analyzer. What is the analyzer you are using? If it
is StandardAnalyzer it drops words like a, the, etc. You can use the
SimpleAnalyzer
and check.
(I am not very sure because I am also new to Lucene :)
On Tue, Aug 5, 2008 at 10:04 AM, SoupErman [EMAIL PROTECTED]
18 matches
Mail list logo