Re: Performance measurements

2013-07-25 Thread Arjen van der Meijden
On 24-7-2013 21:58 Sriram Sankar wrote: On Wed, Jul 24, 2013 at 10:24 AM, Jack Krupansky j...@basetechnology.comwrote: Scoring has been a major focus of Lucene. Non-scored filters are also available, but the query parsers are focused (exclusively) on scored-search. When you say filter do you

Re: lucene indexwriter crash

2013-07-25 Thread Michael McCandless
It looks like something is wrong with your IO system? Is this a local drive or a remote mount? IndexWriter tried to create a new file and hit that odd Input/output error... Mike McCandless http://blog.mikemccandless.com On Wed, Jul 24, 2013 at 8:53 PM, ash nix nixd...@gmail.com wrote: Hi,

Re: 2 exceptions in IndexWriter

2013-07-25 Thread Michael McCandless
Can you describe what your test is doing? How do you purge the index? It's best to open IndexWriter with OpenMode.CREATE to purge (rather than remove the files yourself). Lock obtain timed out means another IndexWriter is currently using that directory. Mike McCandless

Re: lucene indexwriter crash

2013-07-25 Thread ash nix
Hi Mike, Thanks for your help. This is remote mount. Do you know possible reasons of why it can crash on remote mounts. Thank, Ashwin On Thu, Jul 25, 2013 at 4:29 AM, Michael McCandless luc...@mikemccandless.com wrote: It looks like something is wrong with your IO system? Is this a local

Re: lucene indexwriter crash

2013-07-25 Thread Michael McCandless
Something must have gone wrong on the remote mount's end, or in the network communications b/w the client and the server? It could really be anything... In general it's riskier and often far lower performance to host the index on a remote mount. It's better to replicate the index locally; the

Re: 2 exceptions in IndexWriter

2013-07-25 Thread Yonghui Zhao
My test case first create an empty disk index folder then feed some doc then do some query. I purge the index by delete all files in the folder. My unit test has several test cases they use same directory in the disk. But it runs one by oneļ¼Œand I dont think there will be 2 threads use the

Re: 2 exceptions in IndexWriter

2013-07-25 Thread Michael McCandless
Are you sure each test always closes the IndexWriter? Still, it's best to have each test uses its own directory to avoid any risk of confusing failures ... Mike McCandless http://blog.mikemccandless.com On Thu, Jul 25, 2013 at 12:24 PM, Yonghui Zhao zhaoyong...@gmail.com wrote: My test case

Re: Performance measurements

2013-07-25 Thread Sriram Sankar
Thanks everyone. I'm trying this out: So searching would become: - Create a Query with only your termA - Create a TermsFilter with all your termB's - execute your preferred search-method with both the query and the filter I don't the get the same results as before - and am still debugging.

need searcher example to read indexes generated by solr

2013-07-25 Thread mlotfi
Hi, I just did the setup for solr in Tomcat, set the schema pointing to a big database, create 50 cores (one for each US state), the indexes are generated. Where can I find an example servlet and a jsp with a form to search those indexes ? thanks, your help is appreciated. -- View this

Re: Performance measurements

2013-07-25 Thread Arjen van der Meijden
Hi Sriram, I don't see any obvious mistakes, although you don't need to create a FilteredQuery: There are plenty of search-methods on the IndexSearcher that accept both a query (your TermQuery) and a filter (your TermsFilter). The way I understand Filters (but I have no advanced in-depth

Re: Question on Lucene hot-backup functionality.

2013-07-25 Thread Marcos Juarez Lopez
Shai and Michael, Thanks for your help. That did the trick, getting the live IndexDeletionPolicy from the live writer config. I also agree with Michael, it's not obvious at all from the docs and/or Lucene in Action book. Maybe this can be clarified on the IndexDeletionPolicy javadocs going

Re: Question on Lucene hot-backup functionality.

2013-07-25 Thread Shai Erera
Well, it's sort of documented on IndexWriterConfig already: * Once {@link IndexWriter} has been created with this object, changes to this * object will not affect the {@link IndexWriter} instance. For that, use * {@link LiveIndexWriterConfig} that is returned from {@link

Re: Question on Lucene hot-backup functionality.

2013-07-25 Thread Michael McCandless
On Thu, Jul 25, 2013 at 3:15 PM, Marcos Juarez Lopez mjua...@gmail.com wrote: Shai and Michael, Thanks for your help. That did the trick, getting the live IndexDeletionPolicy from the live writer config. I also agree with Michael, it's not obvious at all from the docs and/or Lucene in

Re: Performance measurements

2013-07-25 Thread Jack Krupansky
In addition, although I am a bit beyond my expertise here, I believe you should be able to take any query object, including one returned from a query parser, wrap it with a ConstantScoreQuery, and then search on the CSQ to avoid all the scoring overhead. For example, *:* is super fast even