AHMET ARSLAN wrote:
Aaargh. So now i stand between sticking my head into the
source OR writing my own engine (which is not a big deal
becouse my requirements arent that big but it will anyway
set me back a week or so).
There is another way, although it is not a good thing to chance source
Hello
thank you for your response, the field3 was well defined, I just forgot to
reindex my data.
Regards
Sophie
Grant Ingersoll-6 wrote:
On Oct 19, 2009, at 7:21 AM, sophSophie wrote:
Hello,
firstly sorry for my english :)
Since last Friday I try to define in shema.xml a new
On Wed, Oct 21, 2009 at 2:31 PM, Jérôme Etévé jerome.et...@gmail.com wrote:
Hi there,
I'm planning to reindex all my data on my master server everyday, so
here's what I intend to do on the master:
1 - disable replication on the master
2 - Empty the index
3 - Reindex everything
4 -
I have a simple set of docs containing two fields, an id and a price.
When I run a constant score query, such as *:*, I, of course, get a
score back of 1 for all the docs.
If I add a simple Field Value function query to the constant score
query, as in: *:* _val_:price_f, the query norm
Hello all,
I have an odd problem. I have a Solr-index containing songs by various artists.
When I
perform a search for something that starts with a one-letter word I receive no
hits. If
I remove the one-letter word I get hits though.
So for example, if I search for a hard days night or i want
I just tried with Solr 1.4 trunk and it seems to work fine.
a is a stopword... but I'm not sure how stopwords could be messing you up.
For matching song titles, you may want to use a field type with no
stopwords though (there are a lot of common words in song titles I
think).
If you've changed
I am having problem with using the ShingleFIlter. My test document is the
quick brown fox jumps over the lazy dog. My query is my quick brown.
Since both have the term quick brown at term position 2, the query should
match the test document, right? But my query is not returning anything. I
Our application involves lots of live index updates with mixed priority. A
few updates are very important and need to be in the index promptly, while
we also have a great deal of updates which can be dealt with lazily.
The documentation for the commitWithin leaves some room for interpretation.
--- On Wed, 10/21/09, Bill Au bill.w...@gmail.com wrote:
From: Bill Au bill.w...@gmail.com
Subject: Question on ShingleFilter
To: solr-user@lucene.apache.org
Date: Wednesday, October 21, 2009, 6:04 PM
I am having problem with using the
ShingleFIlter. My test document is the
quick brown
On Wed, Oct 21, 2009 at 11:58 AM, Jacob Elder jel...@locamoda.com wrote:
Our application involves lots of live index updates with mixed priority. A
few updates are very important and need to be in the index promptly, while
we also have a great deal of updates which can be dealt with lazily.
Hi Bill,
On 10/21/2009 at 11:05 AM, Bill Au wrote:
I am having problem with using the ShingleFIlter. My test document is
the quick brown fox jumps over the lazy dog. My query is my quick
brown. Since both have the term quick brown at term position 2, the
query should match the test
Are you saying that faceting is faster on a tokenized field? Is this true?
On Tue, Oct 20, 2009 at 2:02 PM, DHast hastings.recurs...@gmail.com wrote:
...
, removing
that facet worked since the field was untokenizd and slow considering how
many values tehre were.
...
View this message in
1 - disable replication on the master
2 - Empty the index
2a - Delete with query *:*
2b - optimize the empty index
3 - Reindex everything
4 - Optimize
5 - enable replication again
2009/10/21 Noble Paul നോബിള് नोब्ळ् noble.p...@corp.aol.com:
On Wed, Oct 21, 2009 at 2:31 PM, Jérôme Etévé
that's what my use case has shown, but i havent done enough experimenting to
know for sure.
the reason the field is untokenized is because i need the full value of an
authors name, example: smith, jones, if it was tokenized and faceted it
would be jones and another entry for smith.
i am
Hi,
I am using Javascript and JSON to submit the solr query. I want to get
the reponse status so if there is a 400 http error, i will issue an
error instead of doing nothing which is very confusing to the user.
Hope I can even grab the message body.
How do i do that?
Thanks.
Elaine
Hi,
I'm investigating several search indexing options and solr looks great but I
have a few questions I couldn't find answers to. To begin I don't think the
near real time features of Lucene are a requirement to start but I do think it
will be a requirement moving forward and I was curious as
On Wed, Oct 21, 2009 at 8:36 PM, entdeveloper
cameron.develo...@gmail.com wrote:
It's my understanding that Solr 1.4, which is to be released any day now,
will be based on version 2.9 of lucene.
Serious bugs were found in Lucene 2.9.0... we are all set to release
when Lucene 2.9.1 is released,
Further without the NRT features present what's the closest I can
expect to real time for the typical use case (obviously this will vary
but the average deploy). One hour? One Minute? It seems like there are
a few hacks to get somewhat close. Thanks so much.
Depends a lot on the
On Wed, Oct 21, 2009 at 10:19 PM, George Aroush geo...@aroush.net wrote:
Depends a lot on the nature of the requests and the size of the index,
but one minute is often doable.
On a large index that facets on many fields per request, one minute is
probably still out of reach.
With no facets,
Thank you guys for your responses. That is what I suspected, that it was
going with the first instance of the document that it sees. I tried setting
up Solr in Eclipse and ran into a couple of issues blocking it from
compiling. I also did some reading, but none of the write ups were very
I don't like the analogy of trying to map an RDB to Solr directly because
they are fundamentally different. Solr stores documents with a unique ID but
no relations to other documents or document stores to allow for
relationships. Therefore, you can denormalize your data and store both
project and
21 matches
Mail list logo
