Hi Samuele, It's not clear for me if your goal is to search on that field (for example, "salary_min:[100 TO 200]") or if you want to show the transformed field to the user (so you want the result of the regex replacement to be included in the search results).
If your goal is to show the results to the user, then (as Ahmet said in a previous mail) it won't work, because the content of the documents is stored verbatim. The analysis only affects the way that documents are searched. If your goal is to search, could you please show us the query that you're using to test the use case? Thanks! *Juan* On Wed, Jun 29, 2011 at 10:02 AM, samuele.mattiuzzo <samum...@gmail.com>wrote: > ok, but i'm not applying the filtering on the copyfields. > this is how my schema looks: > > > > <field name="salary" type="text" indexed="true" stored="true" /> > <field name="salary_min" type="salary_min_text" indexed="true" > stored="true" > /> > <field name="salary_max" type="salary_max_text" indexed="true" > stored="true" > /> > > > <copyField source="salary" dest="salary_min" /> > <copyField source="salary" dest="salary_max" /> > > and the two datatypes defined before. that's why i tought i could first use > "copyField" to copy the value then index them with my two datatypes > filtering... > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Regex-replacement-not-working-tp3120748p3121497.html > Sent from the Solr - User mailing list archive at Nabble.com. >
