Hi Andrew
I am using Spring to define my Quartz job's and triggers. I use
org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean to
specify the targetobject and targetmethod of another java object that is
executed when the tirgger occurs. Since we are using JBoss, the scheduler
Ian, I did see the warnings against using the NativeFSLockFactory on NFS.
I know the the volume is mounted, but I am not sure it is NFS. If I run my
indexing process outside of JBoss I do not see the lock errors, which made
me think it was not using NFS. But I am not sure.
If I don't use
a BooleanQuery, but it requires me to consider every possible pair of terms
(since any one of the terms could be missing)
What about setting minMatch and all the terms as SHOULD - and then
minMatch could be tuned for how many missing terms to tolerate?
See:
Hi Dima,
The example code you mentioned in your other recent email is pretty close.
The only thing you'd probably want to add is access to the CharTermAttribute:
CharTermAttribute termAtt = addAttribute(CharTermAttribute.class);
and then in the loop over ts.incrementToken(), you can get to
Hi,
I have a search scenario in which I search for multiple terms and retain
only those matches that share a common payload. I'm using this to
search for multiple terms that occur all in one sentence; I've stored a
sentence ID in the payload for each token.
So far, I've done so by specifying a
Am 13.12.2012 18:00, schrieb Jack Krupansky:
Can you provide some examples of terms that don't work and the index
token stream they fail on?
Make sure that the Analyzer you are using doesn't do any magic on the
indexed terms - your query term is unanalyzed. Maybe multiple, but
distinct,
Hello,
I have been getting the following lock error when attempting to open an
index writer to add new documents to an index.
org.apache.lucene.store.LockObtainFailedException
Lock obtain timed out:
NativeFSLock@/opt/shared/data/CTXTMNG/PAC_INDEX/lucene/aero/prod/index/write.lock
I believe this
Use SimpleFSLockFactory. See the javadocs about locks being left
behind on abnormal JVM termination.
There was a thread on this list a while ago about some pros and cons
of using lucene on NFS. 2-Oct-2012 in fact.
http://mail-archives.apache.org/mod_mbox/lucene-java-user/201210.mbox/thread
--
