what do you understand when you say optimize? Unless you tell us what
this code does in your case and what you'd expect it doing its
impossible to give you any reasonable answer.
simon
On Fri, Dec 2, 2011 at 4:54 AM, KARTHIK SHIVAKUMAR
wrote:
> Hi
>
> Spec
> O/s win os 7
> Jdk : 1.6.0_29
> Lucen
Hi
>> generated Lucene index
What if u need to upgrade this with More docs
Best approach is Inject the Real path of the Index ( c:/temp/Indexes ) to
the Web server Application via "web.xml"
By this approach u can even achieve
1) Load balancing of multiple Web servers pointing to same
Hi
Spec
O/s win os 7
Jdk : 1.6.0_29
Lucene lucene-core-3.3.0
Finally after Indexing successfully ,Why this Code does not optimize (
sample code )
INDEX_WRITER.optimize(100);
INDEX_WRITER.commit();
INDEX_WRITER.close();
*N.S.KARTHIK
R.M.S.COLONY
BEHIND BAN
Currently we use lucene 2.3.2, the reason why we recreate searcher each time
is that within one server we managed a few thousand independent lucene index
data folders. Those folders have different sizes, the large ones have about
200K docs (but growing).
Thanks very much for helps, Lisheng
-O
On Thu, Dec 1, 2011 at 8:30 PM, Zhang, Lisheng
wrote:
> Hi Simon,
>
> 1) Thanks for suggesting lucene 4.0 feature, we will make use of it as soon as
> we upgrade lucene.
>
> 2) Currently we recreate IndexSearcher for each query, which means recreate
> underlying IndexReader for each query (I s
Hi Simon,
1) Thanks for suggesting lucene 4.0 feature, we will make use of it as soon as
we upgrade lucene.
2) Currently we recreate IndexSearcher for each query, which means recreate
underlying IndexReader for each query (I should have said IndexReader), but
sort performance is OK, s
On Thu, Dec 1, 2011 at 7:36 AM, Zhang, Lisheng
wrote:
> Hi Simon,
>
> Sorry I found that I cannot use payload for this purpose because payload
> can be accessed only through term positions but we did not use timestamp
> for query. Ideally it would be great if we can have some doc-level "payload"
>
I am trying to make some high- (and not so high) level design decisions for my
app that is supposed to check a collection of documents against a set of
terms/queries. Basically, I need to perform a triage of sorts when I would find
only those docs in the collection which have occurrences of at l
