[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557538#action_12557538
]
Otis Gospodnetic commented on LUCENE-794:
-
I re-skimmed this JIRA issue just now.
: I just created the release artifacts (incl. maven artifacts) from the
: 2.3 branch and uploaded the files to
: http://people.apache.org/~buschmi/staging_area/lucene_2_3/rc1/.
Some misc comments while purusing the release artifacts...
1) the release release should use the version number "2.3.0"
Awesome! Thanks everyone who gave feedback already. So far it seems that
rc1 is stable and doesn't cause problems after upgrading from 2.2.
A lot of the major changes in 2.3 are tested implicitly after upgrading,
such as the new DocumentsWriter or background merges. However, there are
a bunch of n
I've built a production index with rc1 and blasted it with lots of
concurrent queries and I've seen no problems. I plan to do a lot more
development and testing with 2.3 in the next few months.
Peter
On Jan 7, 2008 10:27 PM, Michael Busch <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I just created t
: So please help testing the release files on different platforms with
: different JVM versions.
FWIW: i just did a simple jar(s) swap with Solr 1.2 and Solr trunk, basic
searching/highlighting/updating worked fine on the Sole example data (with
and without Solr recompile)
-Hoss
---
Good points. I do have the XML file on a separate disk and do have
several disks available, as well as 4 cores. I was thinking that
putting 4 smaller files on 4 disks with 4 threads running would be
optimal in my case.
I'll also look into the single line idea from Mike.
Thanks,
Grant
On
Grant,
In case there is normally only a single disk to read from, I think
reading the disk should be done by a single thread reading the
data as much as possible in the order that it is stored on disk.
Parsing into lucene docs and adding these docs could be done
in parallel. Last time I tried usi
I think the fastest solution is to pre-process the XML file into a
"one doc per line" file (see the example createLineFile.alg). That's
how I run my perf tests on Wikipedia.
Then, put the line file on a different drive than your index, if you
can. Indexing a line file off an independent IO sys
As one can probably guess, I have been looking at the EnwikiDocMaker a
bit and using it outside of the benchmark suite, as related to the new
contrib/wikipedia stuff. Just wanted to make sure I have a good
basic understanding of what it is doing, because I am looking for ways
to speed it
Michael,
So far it looks good on my side. The indexing speed is almost 2x faster.
Michael Busch wrote:
>
> Uwe Schindler wrote:
>>
>> Thanks, works great with panFMP! Until now, no bugs during
>> harvesting/indexing.
>>
>
>
> Great! Thanks for testing and the feedback!
>
> -Michael
>
>
Hi
I am developing an application using lucene in which i am searching a text
and the output should show total no of matching document ,the path of the
document,and the weight/ranking/strength of the query.like if query entered
is chowder,it should show 34 matching document,path of all those matc
11 matches
Mail list logo
