On Sat, 2011-09-03 at 20:09 +0200, Michael Bell wrote:
> To be exact, there are about 300 million documents. This is running on a 64
> bit JVM/64 bit OS with 24 GB(!) RAM allocated.
How much memory is allocated to the JVM?
> Now, their searches are working fine IF you do not SORT the results. If
hi all,
I am using spellcheck in solr 1.4. I found that spell check is not
implemented as SolrCore. in SolrCore, it uses reference count to track
current searcher. oldSearcher and newSearcher will both exist if oldSearcher
is servicing some query. But in FileBasedSpellChecker
public void bu
Looking at the output of IndexSearcher.explain(Query query, int doc)
might help. One possibility is that your boosts are being swamped by
other scoring factors. Larger boosts might make a difference if that
is the case.
--
Ian.
On Mon, Sep 5, 2011 at 12:12 PM, Akos Tajti wrote:
> Hi All,
>
>
Thanks, I will try.
Ákos Tajti
On Mon, Sep 5, 2011 at 2:39 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> You can use IndexReader's setNorm method?
>
> It's an expert method, and accepts a new byte norm value for the doc X
> field, ie you'll have to compute the right byte value.
You can use IndexReader's setNorm method?
It's an expert method, and accepts a new byte norm value for the doc X
field, ie you'll have to compute the right byte value.
Mike McCandless
http://blog.mikemccandless.com
On Mon, Sep 5, 2011 at 5:12 AM, Akos Tajti wrote:
> Dear List,
>
> I'd like to
Hi All,
I'm setting the boost of our documents in indexing time based upon some
properties. When searching, however, it seems that these index time boosts
are not taken into account. I'm parsing the query with lucene's queryparser
and sending the result directly to the searcher. What might be wron
Dear List,
I'd like to test fine-tune the boosts in the search module of our
application. The problem is that we have many documents and it takes a lot
of time to reindex them. Is there a way to change the index time boosts
(afaik it's stored in the fieldNorm) without actually executing the
reinde
Michael Bell wrote:
> How best to diagnose?
>
>> Call your java process this way
>>java -XX:HeapDumpPath=. -XX:+HeapDumpOnOutOfMemoryError
>> and drag'n'drop the resulting java_pid*.hprof into eclipse.
>> You will get an outline by class for the number and size of allocated
>> objects.
Just lo
On Saturday 03 September 2011 20:09:54 Michael Bell wrote:
> 2011-08-30 13:01:31,489 [TP-Processor8] ERROR
> com.gwava.utils.ServerErrorHandlerStrategy - reportError:
> nastybadthing ::
> com.gwava.indexing.lucene.internal.LuceneSearchController.performSear
>chOperation:229 :: EXCEPTION : java.lang
