Why are you reluctant to set ' indexed="true" ' for that field? It doesn't create another index, it's just another field in your current index. You can surely set ' stored="false" ' in order not to keep a copy of the raw data though...
Indexing fields twice is a common option when treating those fields differently.. Best Erick On Thu, Oct 13, 2011 at 10:12 AM, Victor <scanner...@yahoo.co.uk> wrote: > I looked at the copyfield solution and found it not suitable for what I am > trying for. I defined a new <field> using a <fieldType> that uses a synonym > filter for the query analyzer. Then I used a <copyfield> command to fill it > with the data that I want. Since I do not want to create another index I set > the index parameter to false, "indexed=false". I found that it is impossible > to query on this field (which is logical, since solr does it's querying > based on indexes). > > I guess what I would need is an expansion of the solr functionality of the q > parameter, like: > > q=<field>:<analyzer>:<search term> > > Should I wait for it? :-) > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Multiple-search-analyzers-on-the-same-field-type-possible-tp3417898p3418672.html > Sent from the Solr - User mailing list archive at Nabble.com. >
