Dne Sun, 18 Sep 2005 05:56:24 -0400
Erik Hatcher <[EMAIL PROTECTED]> napsal(a):
> Lucene was recently converted from Bugzilla to JIRA. I'm unfamiliar
> with JIRA's administrative options, but I see that I have
> administrative capability on our installation and have seen the
> "Lucene Notif
[PATCH] BufferedIndexOutput - optimized writeBytes() method
---
Key: LUCENE-435
URL: http://issues.apache.org/jira/browse/LUCENE-435
Project: Lucene - Java
Type: Improvement
Components: Store
Reporter: L
[PATCH] BufferedIndexOutput - optimized writeBytes() method
---
Key: LUCENE-435
URL: http://issues.apache.org/jira/browse/LUCENE-435
Project: Lucene - Java
Type: Improvement
Components: Store
Reporter: L
[ http://issues.apache.org/jira/browse/LUCENE-435?page=all ]
Lukas Zapletal updated LUCENE-435:
--
Attachment: BufferedIndexOutputWriteBytes.patch
The patch in unified format created by:
# .../trunk> svn diff
> [PATCH] BufferedIndexOutput - optimized wr
[
http://issues.apache.org/jira/browse/LUCENE-435?page=comments#action_12329981 ]
Lukas Zapletal commented on LUCENE-435:
---
TestStore runs fine, I will add some testing for writeBytes (since it uses
writeByte). The patch is tested.
> [PATCH] BufferedI
[
http://issues.apache.org/jira/browse/LUCENE-435?page=comments#action_12329976 ]
Lukas Zapletal commented on LUCENE-435:
---
Hold on, I will supply unified patch, I am also working on TestStore to do some
testing.
> [PATCH] BufferedIndexOutput - optimi
Opps, sorry, I thought JIRA is not sending this...
...just ignore this mail. Thanks
--
S pozdravem / Best regards
Lukas Zapletal
sefredaktor / editor-in-chief
LinuxEXPRES - opravdovy linuxovy magazin
www.LinuxEXPRES.cz
tel.:+420 777 003 843
-
I use lucene to index a key word with date object. When I search document,
how could I process the searching result for that field? For example:
index date with
Field field = Field.Keyword("created", new Date);
.
..
When I search that, I get that field back
Field f = doc.getField("created
Did somebody here successfully integrate the BM25 algoritm in Lucene or
worked on it? I am looking for some knowledge in this area. I am by myself
only using Lucene 1.2 (forced by hardware and VM limitations), but generally
I would be grateful for any kind of knowledge regarding this topic.
Thank
I'm using Lucene 1.9 for the first time (migrating from Lucene 1.4.3) and
building from the latest version in SVN.
How long should "ant test" take? It seems to progress normally, then freezes
after TestWildcard (have been waiting like 20 minutes). The CPU is still
spinning doing something...
ja
On Sep 20, 2005, at 2:57 PM, Yonik Seeley wrote:
I'm using Lucene 1.9 for the first time (migrating from Lucene
1.4.3) and
building from the latest version in SVN.
How long should "ant test" take? It seems to progress normally,
then freezes
after TestWildcard (have been waiting like 20 minu
I had the same problem, but thought an issue was on my end.
Just tried it now, and it went through, all tests passed twice.
Otis
--- Marvin Humphrey <[EMAIL PROTECTED]> wrote:
>
> On Sep 20, 2005, at 2:57 PM, Yonik Seeley wrote:
>
> > I'm using Lucene 1.9 for the first time (migrating from
I lied.
> I had the same problem, but thought an issue was on my end.
> Just tried it now, and it went through, all tests passed twice.
That was on a different machine. I just did svn up, followed by ant
test, and things hang. svn up brought this:
U common-build.xml
U CHANGES.txt
U
src/
It looks like SpanNotQuery's rewrite get the following loop in
IndexSearcher in an infinite loop:
for (Query rewrittenQuery = query.rewrite(reader); rewrittenQuery
!= query;
rewrittenQuery = query.rewrite(reader)) {
query = rewrittenQuery;
}
Got to go make dinner...
Otis
I'm looking into it! Sorry 'bout this hopefully a fix will be
forthcoming...
Erik
On Sep 20, 2005, at 7:46 PM, Otis Gospodnetic wrote:
It looks like SpanNotQuery's rewrite get the following loop in
IndexSearcher in an infinite loop:
for (Query rewrittenQuery = query.rewrite(rea
Yonik,
Thanks for reporting this, and thanks to Otis for pointing me quickly
to the issue. I too had run the tests, but my environment has some
modified code so I chalked up the test issue to my local environment
also. My apologies for not practicing what I preach in this case.
I have c
Hello again,
I've prepared a patch for IndexInput.java, and an accompanying patch
for TestIndexInput.java. I figured I would submit them for
discussion here before filing them via Jira. The patches are
attached to this email; if I find that they get stripped by the
listserv, I'll post t
I wrote:
The patches are attached to this email; if I find that they get
stripped by the listserv, I'll post them on a website.
They got stripped, so here are the links:
http://www.rectangular.com/downloads/IndexInput.patch
http://www.rectangular.com/downloads/TestIndexInput.patch
Marvin Hu
[
http://issues.apache.org/jira/browse/LUCENE-435?page=comments#action_12330060 ]
Doug Cutting commented on LUCENE-435:
-
I voiced some concerns about this patch in:
http://www.mail-archive.com/java-dev@lucene.apache.org/msg02055.html
I don't think thes
Greets,
I don't see any junit tests which address IndexOutput directly. I'm
going to create one unless someone points out a file or portion
thereof that I've overlooked.
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
-
I wrote...
I don't see any junit tests which address IndexOutput directly.
I'm going to create one unless someone points out a file or portion
thereof that I've overlooked.
It would be a lot easier to check the output of IndexOutput if JUnit
could compare byte arrays. :|
I can loop thr
import java.util.Arrays;
...
Arrays.equals(array1, array2);
On 9/21/05, Marvin Humphrey <[EMAIL PROTECTED]> wrote:
> I wrote...
>
> > I don't see any junit tests which address IndexOutput directly.
> > I'm going to create one unless someone points out a file or portion
> > thereof that I've ove
22 matches
Mail list logo
