Why is this code not returning any results?
//Create the query and search
QueryParser queryParser = new QueryParser("contents", new
StandardAnalyzer());
Query query = queryParser.parse(searchCriteria);
Yep. I searchcriteria and the category type value exists for a given
document.
--
View this message in context:
http://www.nabble.com/TermsFilter-Usage-Question-tp22230841p22231524.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
Shooot... The category type was stored by the not indexed! :teeth:
The moment I flipped the flag of categoryType field to analyzed. I was able
to pull the results.
--
View this message in context:
http://www.nabble.com/TermsFilter-Usage-Question-tp22230841p22231549.html
Sent from the Lu
Is there an existing Utility class which will sort a collection of ScoreDocs
? I have a result set (array of ScoreDocs) stored in JVM and want to sort
them by relevanceScore. I do not want to execute the query again. The stored
result set is sorted by another term and hence the need.
Would highly
of Java code.
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>> -----Original Message-
>> From: Chetan Shah [mailto:chetankrs...@gmail.com]
>> Sent: Monday, March 02, 2009 4:47 PM
I am initiating a simple search and after profiling the my application using
NetBeans. I see a constant heap consumption and eventually a server (tomcat)
crash due to "out of memory" error. The thread count also keeps on
increasing and most of the threads in "wait" state.
Please let me know what
No, I have a singleton from where I get my searcher and it is kept through
out the application.
Michael McCandless-2 wrote:
>
>
> Are you not closing the IndexSearcher?
>
> Mike
>
> Chetan Shah wrote:
>
>>
>> I am initiating a simple search and aft
After reading this forum post :
http://www.nabble.com/Lucene-Memory-Leak-tt19276999.html#a19364866
I created a Singleton For Standard Analyzer too. But the problem still
persists.
I have 2 singletons now. 1 for Standard Analyzer and other for
IndexSearcher.
The code is as follows :
package w
ce?
>
> You're using a RAMDirectory to hold the entire index... how large is
> your index?
>
> Mike
>
> Chetan Shah wrote:
>
>>
>> After reading this forum post :
>> http://www.nabble.com/Lucene-Memory-Leak-tt19276999.html#a19364866
>>
>&
;
> So, to start what is your heap currently set at for tomcat?
>
> Secondly, if you try to increase it to a more reasonable value (say 512M
> or 1G) do you still run into this issue?
>
> Matt
>
> Chetan Shah wrote:
>> The stack trace is attached.
>>
my sanity :) */
parser = null;
fis.close();
fis = null;
f = null;
/* till here */
return title;
Chetan Shah wrote:
>
> I am initiating a simple search and after profiling the my application
> usin
ity...).
>
> But: if you increase the HEAP do you still eventually hit OOME?
>
> Mike
>
> Chetan Shah wrote:
>>
>> After some more researching I discovered that the following code snippet
>> seems to be the culprit. I have to call this to get the "title&quo
index itself
and found out that the OOME problem is gone.
I tested this with 256MB heap size.
Thank you all for your valuable advice and help.
Chetan Shah wrote:
>
> I am initiating a simple search and after profiling the my application
> using NetBeans. I see a constant heap consum
13 matches
Mail list logo