[ https://issues.apache.org/jira/browse/SOLR-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830049#action_12830049 ]
Noble Paul commented on SOLR-1758: ---------------------------------- other than the tag names , nothing much can be done w/ a schema. Most of the configuration is in the attributes, and they are arbitrary. So i'm not sure how far it can help > schema definition for configuration files > ----------------------------------------- > > Key: SOLR-1758 > URL: https://issues.apache.org/jira/browse/SOLR-1758 > Project: Solr > Issue Type: New Feature > Components: contrib - DataImportHandler > Affects Versions: 1.4 > Reporter: Jorg Heymans > > A schema definition would be able to spot the subtle error in below config > {code} > <dataSource name="ora" driver="oracle.jdbc.OracleDriver" url="...." /> > <datasource name="orablob" type="FieldStreamDataSource" /> > <document name="mydoc"> > <entity dataSource="ora" name="meta" query="select id, filename, > bytes from documents" > > <field column="ID" name="id" /> > <field column="FILENAME" name="filename" /> > <entity dataSource="orablob" processor="TikaEntityProcessor" > url="bytes" dataField="meta.BYTES"> > <field column="text" name="mainDocument"/> > </entity> > </entity> > </document> > {code} > Also, many xml editors support auto completion based on schema definition so > it would be easier to create configuration without constantly having to refer > to javadoc or samples from the distribution. > This applies equally to schema.xml and solr-config.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.