Hi,
i have recently moved Solr at one of our customers to a MultiCore environment
running 2 indexes. Since then, we seem to be having problems with locks not
being removed properly, .lock files keep sticking around in the index
directory.
Hence, any updates to the index keep returning 500
Hi everyone,
i was wondering if the following was possible somehow:
dynamicField name=*_m_i type=text indexed=true stored=false
required=false multiValued=true/
dynamicField name=*_m_i_f type=string indexed=true stored=true
required=false multiValued=true/
copyField source=*_m_i dest=*_m_i_f/
I figured out where the problem was. The destination wildcard was actually
matching the wrong field. I changed the fieldnames around a bit and now
everything works fine. Thanks!
-Ursprüngliche Nachricht-
Von: kenf_nc [mailto:ken.fos...@realestate.com]
Gesendet: Mittwoch, 14. Juli
For now I need them, I will however most likely (as suggested by Ahmet Arslan),
create another boolean field to get rid of them, just simply due to the fact
that I am switching to Solr 1.4 frange queries.
On the topic of frange queries, is there a way to simulate the date range
wildcards here?
((valid_from:[* TO 2010-04-29T10:34:12Z]) AND
(valid_till:[2010-04-29T10:34:12Z TO *])) OR ((*:*
-valid_from:[* TO *]) AND (*:* -valid_till:[* TO *])))
I use the empty checks for datasets which do not have a
valid from/till range.
Is there any way to get this any faster?
I can
-
From: Jan Simon Winkelmann [mailto:winkelm...@newsfactory.de]
Sent: Tuesday, April 27, 2010 2:41 PM
To: solr-user@lucene.apache.org
Subject: copyField for dynamicFields
Hi,
i have the following configured in my schema.xml:
dynamicField name=*_i type=text indexed=true stored=false
Hi,
I'm having some problems understanding why certain search queries don't return
any results.
I have a field of type text, which is defined like this:
fieldType name=text class=solr.TextField
positionIncrementGap=100
analyzer type=index
charFilter
Hi,
I'm having a strange problem when indexing data through our application.
Whenever I post something to the update resource, I get
Unexpected character 'a' (code 97) in prolog; expected '' at [row,col
{unknown-source}]: [1,1], html
head
meta http-equiv=Content-Type content=text/html;
-Simon Winkelmann
2010/2/10 Jan Simon Winkelmann winkelm...@newsfactory.de:
I am (still) trying to get JMX to work. I have finally managed to get a Jetty
installation running with the right parameters to enable JMX. Now the next
problem appeared. I need to get Solr to register ist MBeans with the Jetty
: My parameters look like this (running the Solr example):
:
: java -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=6060
: -Dcom.sun.management.jmxremote.authenticate=false
: -Dcom.sun.management.jmxremote.ssl=false -jar start.jar
What implementation/version of java are you
very much in advance
Jan-Simon Winkelmann
I'm not sure, theoretically fields with a null value
(php-side) should end
up not having the field. But then again i don't think it's
relevant just
yet. What bugs me is that if I add the -puid:[* TO *], all
results for
puid:[0 TO *] disappear, even though I am using OR.
- operator does not
Hi there,
i have a field defined in my schema as follows:
field name=puid type=integer indexed=true stored=false
required=false /
Valid values for the fields are (in theory) any unsigned integer value. Also
the field can be empty.
My problem is, that if I have (puid:[0 TO *] OR -puid:[* TO *])
bugs me is that if I add the -puid:[* TO *], all results for
puid:[0 TO *] disappear, even though I am using OR.
Best,
Jan
On Jan 25, 2010, at 7:02 AM, Jan-Simon Winkelmann wrote:
Hi there,
i have a field defined in my schema as follows:
field name=puid type=integer indexed=true
=*_index_stored type=text indexed=true stored=true
required=false /
Thanks in advance!
Jan-Simon Winkelmann
16 matches
Mail list logo