: it still dont make any change on the boost value, for information i use
: luke.jar to see if the value had change
i'm not sure what you mean you're using luke to see if hte value has
changed ... boosts aren't stored in the index (they are used to compute a
fieldNorm) so there's nothing for luke
: It's the index time boost, rather than query time boost. This short example
: shows the behaviour of searches for
A... index boosts! ... totally didn't occur to me that was what you
were talking about. Yes: it makes sense that if you give a field an index
boost of 0.0f you won't be able t
: The query parser produces the correct query with the parenthesis.
: But, I'm still looking for a fix for this. I could use some advice on where
: to look in QueryParser to fix this.
the best advice i can give you: don't use the binary operators.
* Lucene is not a boolean logic system
* Boo
please do not cross post questions about using the Lucene API to both the
user and dev mailing lists -- the user list is the correct place to ask
questions about behavior you are seeing that you think may be a bug.
-Hoss
-
T
Adding a MatchAllDocsQuery instance to your boolean query if all clauses
are prohibited is in fact still the best way to do a purely negative
query.
the trunk makes this easier by adding MatchAllDocsQuery syntax to the
query parser...
*:* -description:plot
-Hoss
Hi,
This is a newbie-level question.
I want to construct a query, which returns the results sorted as follows:
1. Results having "all the terms" of the query string in title should be
listed first
2. Results having "any of the terms" of the query string in the title
should be listed next.
3. Res
Well, in the normal course of events, things like deleteDocuments(Term)
shouldn't throw an exception unless I've screwed up. In my experience,
Lucene usually gracefully handles "normal" error cases. In this case, there
not being any underlying documents that match on Term is, I believe, handled
by
Hi,
I was implementing some calls to Lucene, though was
curious if there was
some documentation I was missing that indicated why a
method throws an
exception.
Example, IndexReader - deleteDocuments() - what is the
root cause as to
why it throws IOException?
I'm trying to utilize this info to
I'm looking for a way to search by a field's internal TF vector
representation.
MoreLikeThis does not seem to be what I want-- it constructs a text
query based on the top scoring TF-IDF terms. I want to query by TF
vector directly, bypassing the tokens.
Lucene understandably has knowledge
Miles Efron wrote:
I really don't know why os x could have induced those kinds of
filesystem issues. i assumed that since i had switched over to the
intel architecture that perhaps something was going on with the
JVM...everything involved in the process was mac; local filesystem, etc.
but i'
I really don't know why os x could have induced those kinds of
filesystem issues. i assumed that since i had switched over to the
intel architecture that perhaps something was going on with the
JVM...everything involved in the process was mac; local filesystem, etc.
but i'm fairly sure tha
This is a ton of discussion on this if you search the lucene user list
(QueryParser and precendence and the 'binary' operators). I have seen
many mentions of the precedence parser still having open issues but no
mention of what those issues are.
Peter Keegan wrote:
OK, I see that I'm not the f
Miles Efron wrote:
You rule. Swapping out the nightly build seems to have fixed the
problem... tried it on two problematic cases and both worked.
Phew!
For the record, I'm running mac os 10.4.8.
Uh-oh, I can't explain why you would hit these errors on OS X 10.4.8;
we have only seen these
OK, I see that I'm not the first to discover this behavior of QueryParser.
Can anyone vouch for the integrity of the PrecedenceQueryParser here:
http://svn.apache.org/repos/asf/lucene/java/trunk/contrib/miscellaneous/src/java/org/apache/lucene/queryParser/precedence/
Thanks,
Peter
On 2/1/07, Pe
Mike,
You rule. Swapping out the nightly build seems to have fixed the
problem... tried it on two problematic cases and both worked.
For the record, I'm running mac os 10.4.8.
Do you know if the lockless commits will be included in the next
stable release?
Thanks so much!
-Miles
On Feb
Miles Efron wrote:
i seem to be having a problem analogous to this one (no answer that i see):
http://www.gossamer-threads.com/lists/lucene/java-user/32268?search_string=cannot%20overwrite;#32268
trouble is, i just put lucene on my new macbook pro and am having the
problem that if i bui
i seem to be having a problem analogous to this one (no answer that i
see):
http://www.gossamer-threads.com/lists/lucene/java-user/32268?
search_string=cannot%20overwrite;#32268
trouble is, i just put lucene on my new macbook pro and am having the
problem that if i build a large index, i
Has anyone integrated a crawler with lucene that they had success with? I
cannot use Nutch, since 60% of our searchable content is contained in a
database. I need to do a hybrid between database indexing and website
crawling. I would be just crawling one domain with a given set of
directorie
Correction:
The query parser produces the correct query with the parenthesis.
But, I'm still looking for a fix for this. I could use some advice on where
to look in QueryParser to fix this.
Thanks,
Peter
On 2/1/07, Peter Keegan <[EMAIL PROTECTED]> wrote:
I have discovered a serious bug in Que
I have discovered a serious bug in QueryParser. The following query:
contents:sales && contents:marketing || contents:industrial &&
contents:sales
is parsed as:
+contents:sales +contents:marketing +contents:industrial +contents:sales
The same parsed query occurs even with parenthesis:
(contents:
Please, do not ever, under any circumstances at all, cross post a
message to all of these lists -- there is absolutely no reason for it, and
doing so will most likely only make people mad and uncooporative.
if you are trying to use Java Lucene, then post your message to java-user
list. if you ar
Dear all,
I am happy to send my first email to Lucene community as after subscribing
to the mailing list, I haven't actually joined the community, just standing
aside and following many intersting threads.
As part of my school project, I am intending to make some improvements in
Lucene source co
Dear all
I am happy to send my first email to Lucene community after some time
standing aside, following many interesting discussions.
As part of my school project, I am intending to make some improvements in
Lucene source code, and I need some advices on how significance my
modification work wo
Kadlabalu, Hareesh wrote:
Hi,
I am starting to work with Lucene 2.0 and I noticed that we can no
longer create an FSDirectory using a LockFactory.
Could someone point me to some discussion or documentation related to
locking and what has changed in terms of best practices? It appears that
the
Hi,
I am starting to work with Lucene 2.0 and I noticed that we can no
longer create an FSDirectory using a LockFactory.
Could someone point me to some discussion or documentation related to
locking and what has changed in terms of best practices? It appears that
the only way to build custom lock
Oh is it?I didn't know about that...so Is it means I cant use this Mobile HDD..
Damien McCarthy <[EMAIL PROTECTED]> wrote: FAT 32 imposes a lower file size
limitation than NTF. Attempts to create
files greater that 4Gig on FAT32 will throw error you are seeing.
-Original Message-
From:
I am also only novice, but that should work for you.
One row in your table ==> one doc in lucene:
I would indice it like that for one row/document:
Document doc = new Document();
doc.add(new Field("prod_Id
doc.add(new Field("prod_name...
...
writer.addDocument(doc);
Now check your index
I see now :)
Thank u all for your support
__
Matt
-Original Message-
From: WATHELET Thomas [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 3:28 PM
To: java-user@lucene.apache.org
Subject: RE: Deleting document by file name
* This
FAT 32 imposes a lower file size limitation than NTF. Attempts to create
files greater that 4Gig on FAT32 will throw error you are seeing.
-Original Message-
From: maureen tanuwidjaja [mailto:[EMAIL PROTECTED]
Sent: 01 February 2007 14:22
To: java-user@lucene.apache.org
Subject: Building
do something like this:
public class Index extends IndexModifier { ...
public int deleteDocuments(String field, String value) throws
IOException {
return super.deleteDocuments(new Term(field, value));
}
use like this :
index.deleteDocuments(filed name, field value);
_
Dear All,
I was indexing 660,000 XML documents.The unoptimized index file was
successfully built in about 17 hrs...This index file resides in my D drive
which has the free space 38 Gb.This space is insufficient for optimizing the
index file -->I read Lucene documentation said about its
If I have the path of the document,
I cannot find the ID ?
__
Matt
-Original Message-
From: Erick Erickson [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 2:09 PM
To: java-user@lucene.apache.org
Subject: Re: Deleting document by file
Yes you are right
but i have change it to:
Field tiTle = new
Field("title",httpd.getTitle(),Field.Store.YES,Field.Index.TOKENIZED );
tiTle.setBoost(6.1f);
doc.add(tiTle);
---
it st
I haven't played with boosts, but I suspect your ordering is wrong. You've
already added the field to the document before you set the boost. Try
Field f = new Field()...
f.setBoost()
doc.add(f).
writer.addDoc(doc)..
Best
Erick
On 2/1/07, liquideshark <[EMAIL PROTECTED]> wrote:
iam building
HI guys,
I've read on
http://www.nabble.com/Using-NOT-queries-inside-parentheses-tf1234775.html#a3272973
this forum about the problem of using, for example, only a prohibit search
such as
-description:plot
I really would like to get this done on a good manner, I am constructing
queries where e
Believe it or not, you delete items with IndexReader . You can either
delete by document ID or by Term. Be aware that currently open searchers
will still find these documents (even after they have been deleted) until
the *searcher* is closed and reopened.
Erick
On 2/1/07, DECAFFMEYER MATHIEU <[E
iam building up a search engine using lucene 2.0, and iam having problem
using the term boost "setboost" a part of my code is :
and my code is :
doc.add(new
Field("title",httpd.getTitle(),Field.Store.YES,Field.Index.TOKENIZED ));
doc.getField("title").setboost(5.0f);// <=== the boost wont update
Hi,
I have a list of filenames like
Corporate.htm
Logistics.htm
Merchant.htm
that need to be deleted.
For now on I give this list to my Search application that reads the
idnex and give the results, and if the path contains one of the
filenames, I don't display this hit ... Not really proper
Hi Chris,
: If I search for a document where the field boost is 0.0 then the document is
not
: found I just search that field. Is this expected???
you mean you search on: A^0and get no results even though
documents contain A, and if you search on: +A^0 B^1 you see
those d
Thank u Chris for your support.
__
Matt
-Original Message-
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 12:54 AM
To: java-user@lucene.apache.org
Subject: RE: Score
* This message comes from the Internet Net
40 matches
Mail list logo
