: It is strange that I was suggested not to call commit explicitly and leave
: it to the lucene but it seems it has its own disadvantages.
as long as you commit/close the writer cleanly on shutdown you should be
fine ... i don't think you need to be so agressive as to call it on ever X
docs (un
Hi Ian
Thanks for looking into the issue. And you are right. Its not this code
which was causing the issue.
The issue was as follows: (I just successfully performed a test run)
*ISSUE:*
My code had following characteristics.
1. CREATE_OR_APPEND way of opening indexWriter.
2. No explicit call to
If I define a query and filter like this:
Query q = new BooleanQuery()
// populating q
Filter filter = new CachingWrapperFilter( new QueryWrapperFilter( q ) )
given that I don't need score and I do need a cached filter to reuse it
immediately for other calculations, which way of searching would
Hi Sanne,
Thanks, we already have the required patches installed on the Jenkins build
server for testing purposes. In fact it’s a minimum of three bugs. It fixes all
those bugs reported in the issues.
The patch we have installed can be found on LUCENE-3335:
https://issues.apache.org/jira/secure
Code looks fine and will not zap the current contents of indexDir.
Something else must be - another call with OpenMode.CREATE? Where is
indexDir - could tomcat be zapping it on startup? Some other job?
--
Ian.
On Thu, Jul 28, 2011 at 8:12 PM, Saurabh Gokhale
wrote:
> Hi All,
>
> I am using f
Hello,
thanks for the warning, that's a pretty nasty bug.
A patch was made for OpenJDK, if anybody is interested to try it out
that would be great:
http://hg.openjdk.java.net/hsx/hotspot-comp/hotspot/rev/4e761e7e6e12
Regards,
Sanne
2011/7/28 Uwe Schindler :
> Hello Apache Lucene & Apache Solr us
