We could harness solr-646, reusing the <property name='...'>..</property> syntax by creating a scope for field elements when reading the schema. Since properties (the PropertyMap) are stored in the ResourceLoader, it seems we should be able to access them in the useful places through the usual suspects(the core, the config, the schema). In the current case, the property would be defined as 'solr.schema.field.state.displaylevel' - generalized as 'solr.schema.field.<field-name>.<extension-property>'. The only extension to the schema would be by allowing 'property' in the useful places. The syntax & usage would not be as clean as adding an attribute but leaves more freedom to extensions in more places (aka can generalize to fied types, etc). I believe I can update the patch quickly if you're interested. Henri
Grant Ingersoll-6 wrote: > > Not at the moment, but this is something I've wanted to do, too. See > http://lucene.markmail.org/message/ed5g5qdfdmgaefrn?q=attributes+schema > > -Grant > > On Jul 31, 2008, at 6:36 AM, Nikhil Chhaochharia wrote: > >> Hi, >> >> I am using SolrJ and the latest build of Solr 1.3 >> I want to add some custom information to schema.xml and then access >> it from within my application. >> >> Ideally, I would like to enhance the field definitions in schema.xml >> to something like >> >> < field name="state" type="text" displaylevel="private" /> >> >> and then be able to access the displaylevel value from my application. >> >> Is there any way of doing this? >> >> Thanks, >> Nikhil > > > > -- View this message in context: http://www.nabble.com/Custom-information-in-schema.xml-tp18751841p18757614.html Sent from the Solr - User mailing list archive at Nabble.com.
