Hi,
I am having trouble indexing files sometimes,
My application is deployed in tomcat and some times when I try to stop and
restart indexing I am getting index lock exception.
Lucene is creating one lock file in temp folder of tomcat , If I delete that
folder it starts working again.
Can any bod
Hi everybody,
I have a little problem when I close my index writer, but I think that
this error not appears everytime in my logs.
Someone have any idea about this?
java.lang.IndexOutOfBoundsException: Index: 56, Size: 12
at java.util.ArrayList.RangeCheck(ArrayList.java:507)
at ja
Dawid Weiss wrote:
I have a very technical question. I need to alter document score (or in
fact: document boosts) for an existing index, but for each query. In
other words, I'd like these to have pseudo-queries of the form:
1. civil war PREFER:shorter
2. civil war PREFER:longer
for these two
On Sep 28, 2005, at 10:54 AM, Renaud Richardet wrote:
Hello,
From our understanding, Lucene uses the Unix Epoch (Jan 1, 1970) and
there are conflicts with dates that pass this line. For one of our
projects, we will need to be able to move past Jan 1, 1970 date as far
as 1857.
Is there any
Since lucene works only with strings, you can simply write your own
string representation of the date (simple mmdd would work just fine)
HTH
Aviran
http://www.aviransplace.com
-Original Message-
From: Renaud Richardet [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 28, 2005 10:
Hello Luke, hello Paul
Thanks for your quick response!
Best,
Renaud
Luke Francl wrote:
>Index your dates as strings (mmdd).
>
>This works better anyway because range searches work over a wider range
>of dates than when you index the full precision.
>
>On Wed, 2005-09-28 at 09:54, Renaud R
Index your dates as strings (mmdd).
This works better anyway because range searches work over a wider range
of dates than when you index the full precision.
On Wed, 2005-09-28 at 09:54, Renaud Richardet wrote:
> Hello,
>
> From our understanding, Lucene uses the Unix Epoch (Jan 1, 1970) and
On Wednesday 28 September 2005 16:54, Renaud Richardet wrote:
> Hello,
>
> From our understanding, Lucene uses the Unix Epoch (Jan 1, 1970) and
> there are conflicts with dates that pass this line. For one of our
> projects, we will need to be able to move past Jan 1, 1970 date as far
> as 1857.
>
Field length isn't stored... It gets folded into the norm (see
Similarity.lengthNorm) along with the boost and indexing time.
A couple of approaches:
a) index the field twice with two different Similarity implementations
b) store term vectors, derive the length from them and store in the
FieldCach
While you're indexing, you can assign each doc with a field that refers to
how long the document is. So, for example, you can add a field named
"docLength" for each document, and assign it with discrete values such as
"veryshort", "short", "medium", "long", "verylong", depending on how
granular you
Hello,
>From our understanding, Lucene uses the Unix Epoch (Jan 1, 1970) and
there are conflicts with dates that pass this line. For one of our
projects, we will need to be able to move past Jan 1, 1970 date as far
as 1857.
Is there any workaround this?
Thanks,
Renaud
--
Renaud Richardet
COO A
Hi.
I have a very technical question. I need to alter document score (or in
fact: document boosts) for an existing index, but for each query. In
other words, I'd like these to have pseudo-queries of the form:
1. civil war PREFER:shorter
2. civil war PREFER:longer
for these two queries, 1. w
Thatz the only alternative I can see now. Thank you for the input.
Jayakumar.V
-Original Message-
From: Peter Gelderbloem [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 28, 2005 17:40
To: [EMAIL PROTECTED]
Subject: RE: Issue with sounds-like queries
You should present all the
I think your best bet for supporting Java 1.3 would be sticking with Lucene
1.4.
> One of the new classes that I am using is the ConstantScoreQuery. I am not
> sure if this is going to be included in Lucene 1.9 or not but this does
> make use of Java 1.4.
w.r.t. java.util.BitSet, it's a pain, and
You can increase the maxClauseCount (default is 1024), or use filters.
HTH
Aviran
http://www.aviransplace.com
-Original Message-
From: tirupathi reddy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 28, 2005 6:50 AM
To: java-user@lucene.apache.org
Subject: Some error while searchin
You should present all the alternatives to the user as well as the
contexts
of each hit in terms of country, state and full name etc. and let them
decide which one they intended.
Peter
-Original Message-
From: Jayakumar.V [mailto:[EMAIL PROTECTED]
Sent: 28 September 2005 12:03
To: Pe
Hi,
The reason I'm using sounds-like queries is that this search feature will be
used by our lobby staff(s), who'll be of different nationalities. No two
users may spell the place name the same way. They may also misspell the
names. To bring out the closest match based on what they've input, I nee
Hello,
While searching if I enter one or two characters. It founds lot of results
as I can say almost all and at that time it is giving the following error.
8028 total matching documents
caught a class org.apache.lucene.search.BooleanQuery$TooManyClauses
with message: null
And search is
May be you should not be using sounds like queries in the first place?
They are supposed to be fuzzy afaik.
-Original Message-
From: Jayakumar.V [mailto:[EMAIL PROTECTED]
Sent: 27 September 2005 14:54
To: java-user@lucene.apache.org
Subject: Issue with sounds-like queries
Hi,
I'm fac
Dear all,
I have been trying to follow some of the developments for the new version
of Lucene (1.9?). My understanding is that this will require Java 1.4. Is
this correct? Is this because of changes to "core" functionality within
Lucene or is it because some new additional classes require Java
20 matches
Mail list logo
