Range query problem

Hello, I have a strange problem with range query PERIOD:[1 TO 9] It works only if the second parameter is equals or less than 9 If it's greater than 9 , it finds no documents Thanks in advance Alex Kiselevsky Speech Technology Tel:972-9-776-43-46 RD, Amdocs - Israel

Re: Range query problem

On Thursday 26 August 2004 11:02, Alex Kiselevski wrote: I have a strange problem with range query PERIOD:[1 TO 9] It works only if the second parameter is equals or less than 9 If it's greater than 9 , it finds no documents You have to store your numbers so that they will appear in the right

RE: Range query problem

Thanks, I'll try it -Original Message- From: Daniel Naber [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 12:59 PM To: Lucene Users List Subject: Re: Range query problem On Thursday 26 August 2004 11:02, Alex Kiselevski wrote: I have a strange problem with range query

Is Lucene right for me ?

Hello! I am currently choosing technology for web crawler and search engine that will index between 1 and 10 million of documents (with storing documents). For some parts of the project I'll most likely choose existing software, for some I'll have to right new code, but at the end it should be

Re: Is Lucene right for me ?

Ivane, Yes, you can use Lucene for this. 10 mil. documents is not much, if you use adequate hardware. You can use boost individual documents (check the javadocs for Document and Field classes). Are you aware of Nutch, though? It sounds like you are not, and Nutch is probably the best tool for

Does lucene support greater than/less than on strings

I'm converting numbers into strings (0001, 0013, etc) but users will want to search using the and . I've been using the range query for this ([0 TO 0013] if a user does 13). But my index is quite large and I get a ToManyBooleanClauses Exception or an out of memory exception if I increase the

RE: memory leek in lucene?

back to biz. Terence, probably u prepared it already or should I do it? Otis, actually it's just a common way to execute a query. If the code is like hits = ms.search(query); or sort = new Sort(SortField.FIELD_DOC); hits = ms.search(query,sort); or even filter =

weird lock behavior

Hi, I experienced following situation: Suddenly my query became too slow (c.10sec instead of c.1sec) and the number of returned hits changed from c. 2000 to c.1800. Tracing the case I've found locking file abc...-commit.lck. After deletion of this file everything turned back to normal

Concurrency in Lucene

Hi, I'm new in Lucene and I want to use in a website to manage some documentation: Bacally users can add or modify existing documents and users can search the documents. And I have some questions about concurrency, I have been reading the FAQ and searching the mailing list. But I still have some

Re: complex searche (newbie)

hi, in general the query parser doesn't allow queries which start with a wildcard Those queries could end up with very long response times and block your system. This is not what you want. I'm not sure if i understand what you want to do. I expect that you have a field within a lucene document

Re: weird lock behavior

hi, the IndexReader class provides some public static methodes to check if an index is locked. If this is the case, there is also a method to unlock an existing index. You could do something like: Directory dir = FSDirectory.getDirectory(indexDir, false); if (IndexReader.isLocked(dir)) {

Re: weird lock behavior

Iouli, This sounds like something that should never happen. It never happens for me at simpy.com - and I use Lucene A LOT there. My guess is that the problem with the commit lock has to do with misuse of IndexReader/Searcher. Like with the memory leak issue, please try isolating the problem in