when embeded the solr in my application last night, i encountered the too
many open file exception just like that said in
"http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200702.mbox/[EMAIL
PROTECTED]". And i used DirectSolrConnection to integrate solr with my
application.
when embeded the solr in my application last night, i encountered the too many
open file exception just like that said in
"http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200702.mbox/[EMAIL
PROTECTED]". And i used DirectSolrConnection to integrate solr with my
application.
Dynamic field types are field types that act as proxies to other field
types. The choice of the field type to use is done on a per document basis
and is dependent of the values of the document's fields.
The use case that led us to this feature is the indexation of documents in
different languages.
Hello,
I've recently developped a cocoon application that search and retrieve
catalogue entries by passing requests to a solr, and then managing its
responses. Quite classical so far. The next step of the project is to build
another application that should be able to interrogate several others of
- browsing through the web came I accross an application called the Lucene
Web Service : what do you think of it ? (its goal seems precisely to query
multiple indices, it thus would be the thing I'm searching for ; but
considering the scale of this project, I think I'd prefer to base my work on
Why can't you choose the proper field in your application and keep
separate fields per language? Putting them all in the same field,
regardless of language, is not a good idea in my opinion because it is
more than likely going to skew your statistics and lower your relevance.
That being sa
Grégoire, I believe the answers to your first 2 questions are both positive.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Grégoire Neuville <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Friday, February 29, 2008 6:38:50 AM
>
We will review the java settings. The current settings are a bit low - but
the indexed typically does not reach even 50% of the allocated 1024MB Max
Heap.
Yes the index is large - only 3 fields are stored - and I have set the
positionIncrementGap to 50 (down from 100) in an attempt to reduce ind
We are a bit concerned regarding the index size. At least no response (so
far) as indicated that the size is unmanagable. We killed the process -
will move to Java6 - and will use vmstat to monitor the new optimization
process.
At what index size would you begin to worry? Or is it a combinatio
Yes indeed - it was spending all of its time in garbage collection. We will
be moving to Java6.
Thanks for your suggestion.
Frances
Yonik Seeley wrote:
>
> Have you checked if this is due to running out of heap memory?
> When that happens, the garbage collector can start taking a lot of CPU.
Thanks for your response Grant.
You are right, depending of the language we could index the text in a
specific field. At request time, we would then ask all the fields for the
query.
I see however a few possible problems with this approach. By order of
decreasing importance:
- Influence on relev
On Fri, Feb 29, 2008 at 12:45 AM, Walter Underwood
<[EMAIL PROTECTED]> wrote:
> Good point. My numbers are from a full rebuild. Let's collect maximum
> times, to keep it simple. --wunder
You may see more variation than you expect since optimization is done
in stages of mergeFactor segments. In t
In solrconfig.xml, configure a listener for "postOptimize" but not for
"postCommit". That listener runs snapshooter. You will only create
snapshots after an optimize. That's what I do.
wunder
On 2/29/08 11:38 AM, "Alex Benjamen" <[EMAIL PROTECTED]> wrote:
> OK, I'll give it a shot... Couple of i
OK, I'll give it a shot... Couple of issues I see with the snappuller:
1. When the master performs a commit, and then optimize, there is nothing to
prevent
snappuller to pul a non-optimized index?
2 Do uncommitted updates constitute a different index version... suppose I post
10 XML
fi
I'm looking at snappuller script and the only thing I see it doing is managing
the snapshot
pulling via rsync.
And then once the new distribution is in ${data_dir}/${name}-wip it simpy moves
it to the
index dir:
# move into place atomically
mv ${data_dir}/${name}-wip ${data_dir}/${name}
What
Hi guys,
Who knows how to use >, <, >= ... operations in solr or lucene?
I am using range operation. Is that the only way?
Age:[10 TO 9]
Thanks,
Otis Gospodnetic wrote:
>
> It's a little hard to read that message, but if I were you I'd go to the
> Solr admin page, analysis section, enter your query, and see what index
> and query time analyzers spit out. I think that should at least give you
> some hints.
>
> Otis
>
> --
> Sematext -
Hi,
I'm trying to find a way to paginate through facet values. But it seems that
there is not a way to get the total number of values (numFound) under a
given facet field? For example, if I have a facet field called
"composition_era_facet" and the values are:
15th Century
16th Century
17th Centur
On Fri, Feb 29, 2008 at 5:37 PM, Matt M. <[EMAIL PROTECTED]> wrote:
> I'm trying to find a way to paginate through facet values. But it seems that
> there is not a way to get the total number of values (numFound) under a
> given facet field?
If you include zero counts, it's the same for every q
ok i have compared the DirectSolrConnection .java and SolrDispatchFilter.java,
and found that the DirecSolrConnection really do not call the req.colse() as
SolrDispatchFilter do, which is said to free the resources. i guess it is the
leak of handlers,i will try and see.^_^
- Original Message
i think i have just fix the problem, and close method in Directsolrconnection,
and now the number of handler keeps stable. hope it would help other solr
users ^_^
- Original Message -
From: "陈亮亮" <[EMAIL PROTECTED]>
To:
Sent: Saturday, March 01, 2008 9:33 AM
Subject: Re: too many open
I just committed a fix for this.
Thanks for tracking this down!
-Yonik
2008/2/29 陈亮亮 <[EMAIL PROTECTED]>:
> ok i have compared the DirectSolrConnection .java and
> SolrDispatchFilter.java, and found that the DirecSolrConnection really do not
> call the req.colse() as SolrDispatchFilter do, whic
22 matches
Mail list logo