: search = "3 D" OR "3D" ? Reason being, by default, a search for "3D" is
: being split
: into "3 D".
these seems to relate to your other recent question ... Solr is not
splitting "3D" into "3 D" by default at query time just for hte hell of it
... it's doing that because it's what the analyzer c
: (1) How does one ensure that Solr treats words like .Net and 3D correctly ?
: Right now, they get
: translated into Net and 3 d respectively.
Solr doesn't do anything special with your input by default -- it only
does what your schema.xml tells it to do .. if you use the example schema,
then som
Expect it to support other language like chinese.
maybe solr facet can config like this when it support other language.
title:"诺基亚"
or
title:'诺基亚'
or
title:诺基亚
--
regards
jl
Hi,
Didn't see anyone answering your questions...
1) You'll have to write your own analyzer and tokenizer that does the right
thing for your input. From what you described so far, maybe you can simply use
the WhitespaceAnalyzer or some such.
2) Again, you'd have to write your own analyzer and
Is is possible to specify that a term to be looked up in alternate ways" -
e.g.
search = "3 D" OR "3D" ? Reason being, by default, a search for "3D" is
being split
into "3 D".
Thanks.
--
View this message in context:
http://www.nabble.com/OR-condition-in-search...-tf3695012.html#a10332814
Sent
On 5/4/07, Jack L <[EMAIL PROTECTED]> wrote:
I use this to sort the facet field values against count in
reverse order in Python:
sorted(facet_field_values.items(), lambda x, y: cmp(x[1], y[1]), reverse = True)
FWIW, the key= parameter is generally more efficient for python 2.4+:
sorted(facet.
I use this to sort the facet field values against count in
reverse order in Python:
sorted(facet_field_values.items(), lambda x, y: cmp(x[1], y[1]), reverse = True)
Thursday, May 3, 2007, 6:18:05 PM, you wrote:
> We resort it in solr-ruby:
>def field_facets(field)
> facets = []
>
(1) How does one ensure that Solr treats words like .Net and 3D correctly ?
Right now, they get
translated into Net and 3 d respectively.
(2) Is it possible to force Lucene to treat a multiword (e.g. Ruby on Rails)
as one word ? I am not sure
if there is a mechanism to do this by creating a speci
Hello,
I'm interested in FederatedSearch on wiki:
http://wiki.apache.org/solr/FederatedSearch
I would like to understand the design concept of this article properly,
and I have some questions:
1. What does "multi-step" mean?
e.g.
Nice to haves:
Retain ability to have complex *multi-step* query
