Hello Tuan,
did you delete, commit and reindex your index after you've changed anything?
Can you show us the schema.xml? It could be possible, that you are applying
different filters on index- and querytime.
Kind regards
- Mitch
--
View this message in context:
http://lucene.472066.n3.nabble.
Hi Mitch,
I am using the example schema exactly as it is distributed with Solr.
Yes I deleted and reindex using java -jar post.jar
after changing any thing in schema.xml
On Apr 24, 2010, at 4:31 AM, MitchK wrote:
Hello Tuan,
did you delete, commit and reindex your index after you've c
Sorry I should have mentioned that Iam using 1.4 official release.
On Apr 24, 2010, at 4:31 AM, MitchK wrote:
Hello Tuan,
did you delete, commit and reindex your index after you've changed
anything?
Can you show us the schema.xml? It could be possible, that you are
applying
different
If its worth mentioning here, in my case the disk read speeds seemed to have
a really noticeable effect on the query times. What disks are you planning
on using? Also, as Otis has already pointed out, I doubt if a single box of
that capacity can handle 100-700 queries per second.
On Fri, Apr 23, 2
thanks Otis for answering,
Do you have any helpful links on how to build one? Any helpful advice on
what to look into?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Multiple-query-searches-in-one-request-tp745827p747708.html
Sent from the Solr - User mailing list archiv
I can't reproduce the error, Tuan.
However, I think if the analysis.jsp shows something different than the real
results, I think the index is not in the state you are expecting he is.
Did you also commit your changes?
What about the "includes"-field. Does the error also occurs there?
- Mitch
-
Just an idea: try to query for *:* - did you see there any data?
--
View this message in context:
http://lucene.472066.n3.nabble.com/mix-cased-search-terms-tp747279p747763.html
Sent from the Solr - User mailing list archive at Nabble.com.
Tuan, since your example follows a stopword, it makes me think its this
bug: https://issues.apache.org/jira/browse/SOLR-1852
On Sat, Apr 24, 2010 at 7:11 AM, Tuan Nguyen wrote:
>
>
> Sorry I should have mentioned that Iam using 1.4 official release.
>
>
> On Apr 24, 2010, at 4:31 AM, MitchK wro
Robert, thank you very much. You made my day. Indeed that is the
problem.
I tried to simplified the doc to just containing the term PhD and
posting variations of the same doc to see if we're getting the same
symptoms.
The following works:
1
PhD
PhD
PhD
PhD
PhD
PhD
1
1
Big thanks to everyone for pitching in to help me resolve the issue
quickly.
On Apr 24, 2010, at 9:24 AM, Robert Muir wrote:
Tuan, since your example follows a stopword, it makes me think its
this
bug: https://issues.apache.org/jira/browse/SOLR-1852
On Sat, Apr 24, 2010 at 7:11 AM, Tuan Ng
Villemos, Gert wrote:
I want to build a function expression for a dismax request handler 'bf'
field, to boost the documents if it is referenced by other documents.
I.e. the more often a document is referenced, the higher the boost.
Something like
linear(query(myQueryReturningACountOfHowO
: on indexing these are passed through a synonym filter that has this line
: saturday night live => snl, saturday night live
: i now end up with four tokens
: [saturday, 0, 19], [snl, 0, 19], [night, 0, 19], [live, 0,19]
:
: what i want is
: [saturday, 0,8], [snl, 0,19], [night, 9, 14], [live, 1
: How does one do this? UpdateHandler doesn't override the init method
: like SearchHandler.
UpdateHandler isn't Request Handler, it's a differnet beast entirely (that
wasn't as well thought out)
Looking at SolreCore it looks like nothing was ever done to make it
support init options, but the
Hi,
I have about 2 million documents in my index. I want to search them by a
string field. Every document have this field such as 'LB681' .
The field is a dynamic Field which type is string. So, in solr/admin , I do
search by using " PartNo_s:L* " which means started with L,
I can get the r
*Given:*
- 1 database per client (business customer)
- 5000 clients
- Clients have between 2 to 2000 users (avg is ~100 users/client)
- 100k to 10 million records per database
- Users need to search those records often (it's the best way to navigate
their data)
*The Question:*
15 matches
Mail list logo