.
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira/browse/LUCENE-2280
> Project: Lucene - Java
> Issue Type: Bug
ve a look at that and let me know if anything else can be
fine tuned.
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira
if i disable the optimize (remove the call to
IndexWriter.optimize() from my code) will that create any problem in the long
run? if yes what kind of problems it may create?
Most apps never need to optimize.
You should only optimize if your search performance is not good enough, and
really, be
JRE bug, There are few points which i
need some advise
1. To fix this issue if i disable the optimize (remove the call to
IndexWriter.optimize() from my code) will that create any problem in the long
run? if yes what kind of problems it may create?
2. Just by knowing the scenario, that aft
mmit() internally.
Are you saying you see the same exception on 3.0, using the IBM JRE? Can you
try with the Sun JRE?
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https:
un)
JRE.
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira/browse/LUCENE-2280
> Project: Lucene - Java
> Issue Type: Bug
d as lucene.zip.
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira/browse/LUCENE-2280
> Project: Lucene - Java
>
[
https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ritesh Nigam updated LUCENE-2280:
-
Attachment: lucene.zip
Lucene infostream log file.
> IndexWriter.optimize() thr
r my application and index file got
deleted, this time had turned on the infostream on for indexwriter, attaching
the infostream log file.
> IndexWriter.optimize() throws NullPointerException
> --
>
>
upgraded to the newer version of lucene, but probably i will try
3.0.0 version of lucene in future.
OK.
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
>
er version of lucene, but probably i will try
> 3.0.0 version of lucene in future.
>
> > IndexWriter.optimize() throws NullPointerException
> > --
> >
> > Key: LUCENE-2280
> > URL: ht
n of lucene in future.
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira/browse/LUCENE-2280
> Project: Lucene -
FS of the segment flushed
during close.
Are you using autoCommit=true or false?
The fact that this only happens on Windows is telling is there a virus
checker running on this machine?
It'd also be good to know if this still happens on newer versions of Lucene.
I am logging it in catch block and then finally closing the
indexwriter.
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira
the latest updates to the IBM 1.6 JRE?
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira/browse/LUCENE-2280
> Pr
[
https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ritesh Nigam updated LUCENE-2280:
-
Attachment: lucene.jar
lucene.jar my application is using
> IndexWriter.optimize() thr
sing for my application.
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira/browse/LUCENE-2280
> Project: Lucene - Java
>
ce there is no index file exists
after the NullPointerExcepton, I cannot run CheckIndex.
Does this happen in a Sun JRE?
- I have not yet tested the same scenario on Sun JRE till now.
> IndexWriter.optimize() throws NullPointerException
> --
>
>
it uncovers.
Does this happen in a Sun JRE?
> IndexWriter.optimize() throws NullPointerException
> --
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira/browse/LUCENE-2280
> Project: L
IndexWriter.optimize() throws NullPointerException
--
Key: LUCENE-2280
URL: https://issues.apache.org/jira/browse/LUCENE-2280
Project: Lucene - Java
Issue Type: Bug
Components: Index
to 2.3.2 & 2.4. Thanks Grant!
> IndexWriter.optimize(boolean doWait) ignores doWait parameter
> -
>
> Key: LUCENE-1266
> URL: https://issues.apache.org/jira/browse/LUCENE-1266
>
#x27;ll fix it on 2.4 & 2.3.2. Thanks for catching this!
> IndexWriter.optimize(boolean doWait) ignores doWait parameter
> -
>
> Key: LUCENE-1266
> URL: https://issues.a
[
https://issues.apache.org/jira/browse/LUCENE-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1266:
--
Assignee: Michael McCandless
> IndexWriter.optimize(boolean doWait) igno
IndexWriter.optimize(boolean doWait) ignores doWait parameter
-
Key: LUCENE-1266
URL: https://issues.apache.org/jira/browse/LUCENE-1266
Project: Lucene - Java
Issue Type: Bug
o breaking backwards compatibility.
If it's really important you can always create a custom MergePolicy which does
respect maxMergeDocs during optimize.
> IndexWriter.optimize() does not respect maxMergeDocs
>
>
>
hould block 2.3.
> IndexWriter.optimize() does not respect maxMergeDocs
>
>
> Key: LUCENE-1014
> URL: https://issues.apache.org/jira/browse/LUCENE-1014
> Project: Lucene - Java
>
[
https://issues.apache.org/jira/browse/LUCENE-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1036.
Resolution: Fixed
> Unreleased 2.3 version of IndexWriter.optimize() consis
is good to hear that the MAX_PRIORITY was in fact the issue.
I committed the fix on 10/29 so you should be able to use any nightly build
since then.
> Unreleased 2.3 version of IndexWriter.optimize() consistly throws
> java.lang.IllegalArgumentException out-of-t
changed the priority of my thread from MAX_PRIORITY down to
NORM_PRIORITY
and my IndexWriter.optimize() step completes successfully. So your
patch
is probably correct. When will your patch be included in a nightly
build?
> Unreleased 2.3 version of IndexWriter.optimize() consistly thr
[
https://issues.apache.org/jira/browse/LUCENE-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1036:
---
Fix Version/s: 2.3
> Unreleased 2.3 version of IndexWriter.optimize() consis
the issue here, but
I'll leave this issue open for a while to hopefully hear confirmation back from
the original poster...
> Unreleased 2.3 version of IndexWriter.optimize() consistly throws
> java.lang.IllegalArgumentException out
that fixes it. I also
catch & ignore SecurityException coming out of mergeThread.setPriority
since it's fine if we fail to set the thread's priority.
> Unreleased 2.3 version of IndexWriter.optimize() consistly throws
> java.lang.IllegalArgument
the thread priority of
the threads spawned by ConcurrentMergeScheduler to 1+priority of calling
thread. But, we fail to bounds check that this is <= MAX_PRIORITY.
Are your calling threads being set to MAX_PRIORITY?
> Unreleased 2.3 version of IndexWriter.optimize() consistly
:commit point reached: 1250659
INFO:optimize index
INFO: SEIndexThread(): java.lang.IllegalArgumentException
> Unreleased 2.3 version of IndexWriter.optimize() consistly throws
> java.lang.IllegalArgumentException out-of-t
2.3 version of IndexWriter.optimize() consistly throws
> java.lang.IllegalArgumentException out-of-the-box
>
>
> Key: LUCENE-1036
>
to combine indices in
the end?
> Unreleased 2.3 version of IndexWriter.optimize() consistly throws
> java.lang.IllegalArgumentException out-of-the-box
>
>
>
of IndexWriter.optimize() consistly throws
> java.lang.IllegalArgumentException out-of-the-box
>
>
> Key: LUCENE-1036
> URL: https://issu
Unreleased 2.3 version of IndexWriter.optimize() consistly throws
java.lang.IllegalArgumentException out-of-the-box
Key: LUCENE-1036
URL: https
IndexWriter.optimize() does not respect maxMergeDocs
Key: LUCENE-1014
URL: https://issues.apache.org/jira/browse/LUCENE-1014
Project: Lucene - Java
Issue Type: Bug
Components
Hello All,
I am new to Java Lucene Api. I am writing a heavy test for lucene java
api. The test is to write text data to disk and also create a lucene
index for it. Everytime, I write index file, I do the following:
org.apache.lucene.index.IndexWriter writer = new
org.apache.lucene.index.IndexW
40 matches
Mail list logo
