I'm assuming that this is just one example of many different
kinds of transformations you could do. It *seems* like a variant
of a synonym analyzer, so you could write a custom analyzer
(it's not actuall hard) to create a bunch of synonyms
for your "special" terms at index time. Or you could use th
On Thu, Jan 20, 2011 at 4:08 PM, shm wrote:
> Hi, I have a little problem regarding indexing, that i don't know
> how to solve, i need to index the same data in different ways
> into the same field. The problem is a normalization problem, and
> here is an example:
>
> I have a special character \u
Hi, I have a little problem regarding indexing, that i don't know
how to solve, i need to index the same data in different ways
into the same field. The problem is a normalization problem, and
here is an example:
I have a special character \uA732, which i need to normalize in
two different ways fo
OK, talk of different fields threw me.
To enable a client to turn on/off a specific filter without knowing
what that filter is,
add the following parameter to the query string when you want to turn
the filter on:
fq=
Then add a default for the filter1 param in lucene query syntax (like
+cat:elect
> What field??? or what filter?
> I'm not really sure I still understand what you are trying to accomplish.
> Perhaps if you have some explicit examples of what types of things
> clients would send in as query parameters to Solr, and what types of
> lucene queries you actually want to be generated
On Thu, Feb 21, 2008 at 2:17 PM, Owens, Martin
<[EMAIL PROTECTED]> wrote:
> > Now put filter1 as a default in your handler (same as any other
> > default), and the client can turn on and off filter1 without knowing
> > what exactly it is.
>
> OK so I have to add a new search hander into solrcon
>> This feature was first committed 10/22/07
Great! should be there then.
> Now put filter1 as a default in your handler (same as any other
> default), and the client can turn on and off filter1 without knowing
> what exactly it is.
OK so I have to add a new search hander into solrconfig.xml w
On Thu, Feb 21, 2008 at 1:49 PM, Owens, Martin
<[EMAIL PROTECTED]> wrote:
> > So you could add something like this to your query
> > fq=&fq= > and have the various filters be a default defined in a handler in
> solrconfig.xml
>
> How does this work? I'm still confused from your explanation. Ar
> Can the client send in which filters should be turned on and off, but
> leave the definition of the filters in solrconfig.xml?
The client must set the property, how solr deals with that is how I want it to
work.
> If so, you can get this effect with the new query parser plugin
> framework. P
On Thu, Feb 21, 2008 at 1:20 PM, Owens, Martin
<[EMAIL PROTECTED]> wrote:
> We have a requirement for being able to switch on and off certain filters
> for different searches.
Can the client send in which filters should be turned on and off, but
leave the definition of the filters in solrconfig.
solrconfig.xml and create a different search a bit like the
example but with different filters.
thoughts?
Best Regards, Martin Owens
11 matches
Mail list logo
