one more thing, in code CustomFieldQueryFilter.java, it doesn't loop through same key more than once. It looks like it never expect more than one custom field in the xml.
________________________________ From: Savannah Beckett <[email protected]> To: [email protected] Sent: Sat, August 28, 2010 4:19:59 PM Subject: bug in custom-fields.xml? When I try to add multiple new custom fields in conf/custom-fields.xml, I foud that all keys have to be different for each custom fields. Otherwise, it will just load the last custom field. Is it by design or a bug? If I do this: <entry key="field.name">name</entry> <entry key="field.indexed">no</entry> <entry key="field.stored">no</entry> <entry key="field.tokenized">yes</entry> <entry key="field.boost">1.0</entry> <entry key="field.multi">false</entry> <entry key="field.name">address</entry> <entry key="field.indexed">no</entry> <entry key="field.stored">no</entry> <entry key="field.tokenized">yes</entry> <entry key="field.boost">1.0</entry> <entry key="field.multi">false</entry> Only the last field will be loaded. I have to do this to get it work: <entry key="field1.name">name</entry> <entry key="field1.indexed">no</entry> <entry key="field1.stored">no</entry> <entry key="field1.tokenized">yes</entry> <entry key="field1.boost">1.0</entry> <entry key="field1.multi">false</entry> <entry key="field2.name">address</entry> <entry key="field2.indexed">no</entry> <entry key="field2.stored">no</entry> <entry key="field2.tokenized">no</entry> <entry key="field2.boost">1.0</entry> <entry key="field2.multi">false</entry>
