Hello
When using new QueryParser(...).parse(...) I'd like to get the
position where the error was detected (to show it to the user).
See (and run) the code below.
This is not possible via e.currentToken (that's null). Nevertheless
this position will be printed within the getMessage() method
...
And expect to match document 156297 (search_text==Austell GA, type==1).
...
System.out.println(searcher.explain(query, 156296));
156297 != 156296
Could that be it?
--
Ian.
On Thu, May 22, 2008 at 11:21 PM, Casey Dement [EMAIL PROTECTED] wrote:
Hi - trying to execute a search in
Is this perhaps sort of pre-written response to the question on
SpanNearQuery I sent just a minute ago?
karl
22 maj 2008 kl. 15.00 skrev Grant Ingersoll:
Unfortunately, I haven't had time to work on
https://issues.apache.org/jira/browse/LUCENE-1001
There is a _HALF BAKED_ patch up
Thanks so much for your reply Mr.Miller, that's exactly what I was trying to
accomplish! :-)
I have however, run into another problem now, and thus I have a follow up
question:
My goal is to provide a set of results like google to the user that presents
a set of results with the keyword
Op Friday 23 May 2008 15:19:03 schreef Karl Wettin:
Everything (scores, explainations and not hitting breakpoints while
debugging) seems to point at that SpanNearQuery doesn't use the
scoring of the inner spans. Is this true?
Yes.
If so, is it intentional?
I don't know. The Spans interface
A TokenStream can only be read once unless you wrap it with a
CachingTokenFilter and call reset between uses. So thats what you should do.
- Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Thanks for your reply, can you give an example of how this is done?
Sincerely;
Fayyaz
markrmiller wrote:
A TokenStream can only be read once unless you wrap it with a
CachingTokenFilter and call reset between uses. So thats what you should
do.
- Mark
Hi Stephane
Can you tell me a bit more about the deadlocks you experience with
Hibernate Search. I have not seen such a situation so far and am
interested to see how to fix the problem.
Emmanuel
On May 12, 2008, at 06:13, Stephane Nicoll wrote:
Hibernate Search introduces deadlock with
Hi
Hibernate Search does not pool the Searcher but pools the underlying
IndexReader(s). From what i've seen, a Searcher is stateless and all
the state is kept in the Readers. so this essentially is equivalent to
reusing the searcher.
Out of curiosity why is a pool of Searcher more
On Fri, May 23, 2008 at 6:41 PM, Emmanuel Bernard
[EMAIL PROTECTED] wrote:
From what i've seen, a Searcher is stateless and all the
state is kept in the Readers. so this essentially is equivalent to reusing
the searcher.
You're right, for a normal IndexSearcher, caching the Searcher is
pretty
Hi,
I could able to create create the index . However, when i am trying to
search, i am hitting 0.
Environment : Windows
DB : Oracle
- I have created a directory called : c://dbindex. I am seeing the indexes
are created.
My sql Query fetches just one row
select id, CSC_SITE_ID, ADDRESS1,CITY,
Hi Emmanuel,
Because there are some synchronized methods, like the one that checks whether a
doc is deleted, that get called during search. If you have a pile of threads
(op. p. mentioned 100 threads) there could be contention around those methods.
Otis
--
Sematext -- http://sematext.com/ --
Dear Mr.Miller:
I figured out how to use the CachingTokenFilter and it worked exactly as you
described. Thanks so much once again for sharing your time and expertise!
:-)
All the best.
Sincerely;
Fayyaz
markrmiller wrote:
A TokenStream can only be read once unless you wrap it with a
13 matches
Mail list logo
