Just path. for example.
i have a slaver and have 10 instances which name like solr1, solr2,solr3...
if solr support user define config file 's path..
i will use /usr/solrapp/conf/solr1_solrconfig.xml, solr2_solrconfig.xml,
solr3_solrconfig.xml...and so.
when i test these instance, i just stay
On 4/25/07, Jack L [EMAIL PROTECTED] wrote:
...Maybe it's time to think about upgrading Jetty...
It's in the pipeline, see https://issues.apache.org/jira/browse/SOLR-128
-Bertrand
On 4/25/07, Jack L [EMAIL PROTECTED] wrote:
Are you running a Solr release, or a snapshot? It'd be interesting to
know If you're running code that predates the fix done in SOLR-173. In
my case, on the production system the code is older than that.
I'm running the 1.1.0 release.
Maybe it's
UTF-16 support should not require any changes to the XML parsing.
All XML parsers are required to support that encoding. The real
change is implementing RFC 3023 (XML Media Types) so that the
encoding can be specified over HTTP.
wunder
On 4/23/07 11:13 AM, Mike Klaas [EMAIL PROTECTED] wrote:
Unsubscribe
That is understood.
For people who are not familiar with Java servlet containers, like
myself, the embedded web server takes the least effort to set up.
And jetty is supposed be a production quality quality package, it'll be
great that the default package with jetty can be used for production.
Is there any way to make Solr not throw an Exception when unknown field
names are submitted as a part of an otherwise valid document? Ie. I
have field named 'foo' in my document but it's not in my schema. For
various bookkeeping / tracking purposes I need to annotate the documents
with extra
Mike,
I don't know for sure. But from the symptom, when error 404 happens,
solr seems to still work fine (so does that part of Jetty.) Then those
404'ed pages may have some solr specific logic in it?
Regardless, I think it's a good idea to use a newer, released (not RC)
version in general,
Hello all:
I'm trying to find a record in my index where the 'type' is changelog and
the 'filename' has 'angel' in it.
Expressing this as
type:changelog filename:+angel or filename:+angel* or filename:+*angel
throws a parse error (probably understandably)
type:changelog (filename:+angel or
Enable leading wildcards and try this:
type:changelog AND filename:*angel*
wunder
On 4/25/07 1:34 PM, Michael Kimsal [EMAIL PROTECTED] wrote:
Thanks. I'm still no results with your suggestion though. I also tried
type:+changelog AND ( (filename:angel) OR (filename:angel*) OR
If I have a multiValued field, will it always return all items in the
array, or can I retrieve just those in the document with matching
text?
Thanks,
Jamie
I have large TEI.2 docs that I am indexing. These are journal issuess
with all the typical sections in them. The main unit of organization
and interest is an article which I want to retrieve intact and display
(no problem there).
The question I'm working on is whether to index each article as
On 4/25/07, Jack L [EMAIL PROTECTED] wrote:
...Regardless, I think it's a good idea to use a newer, released (not RC)
version in general, considering 5.1 is one major version behind
Agreed, but note that we don't have any factual evidence that the
Jetty RC that we use is indeed the cause
What OS are you running on?
The solr on the rsync command line is just a label which is defined in
rsyncd.conf on the master. rsyncd.conf is created on the fly by the script
rsyncd-start:
cat EOF ${solr_root}/conf/rsyncd.conf
rsyncd.conf file
uid = $(whoami)
gid = $(whoami)
use
Could someone give advise on a better way to do this?
I have an index of many merchants and each day I delete merchant products
and re-update my database. After doing this I than re-create the entire
index and move it to production replacing the current index.
I was thinking about updating the
On 4/25/07, Jamie Orchard-Hays [EMAIL PROTECTED] wrote:
I have large TEI.2 docs that I am indexing. These are journal issuess
with all the typical sections in them. The main unit of organization
and interest is an article which I want to retrieve intact and display
(no problem there).
The
What it probably boils down to is how you analyzed (or didn't) those
fields.
What is your schema for those fields?
Erik
On Apr 25, 2007, at 4:40 PM, Michael Kimsal wrote:
leading and trailing at the same time don't work. :( This is
supposedly
fixed in a lucene nightly, but I
Doh doh doh doh; sorry :)
Turns out my email clients can't quite keep up with the traffic on
solr-dev and solr-user.
Thanks Yonik.
-Rushabh
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik
Seeley
Sent: Wednesday, April 25, 2007 11:34 AM
To:
3.0.23 yesterday i try and fail.
which version u use,,,i just not use pro version.
2007/4/26, Bill Au [EMAIL PROTECTED]:
Have you tried resin 3.0.x? 3.1 is a development branch so it is less
stable as 3.0.
Bill
On 4/19/07, James liu [EMAIL PROTECTED] wrote:
It work well when i use tomcat
if use customer Analyzer,
u can use solr admin gui, and click analyzer which can help you use customer
analyzer(i use it to be sure my customer analyzer is ok).
if u wanna know query syntax ,,,it same with lucene,,so u can read
http://lucene.apache.org/java/docs/queryparsersyntax.html
now i use admin gui to moniter cache config
i don't know the difference betwin cumulative_ and no *cumulative_* ,,,like
cumulative_inserts and inserts
and i find evictions always show zeroi m curious when it will change and
its meaning
--
regards
jl
21 matches
Mail list logo
