[
https://issues.apache.org/jira/browse/SOLR-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Sokolov updated SOLR-1758:
-------------------------------
Attachment: config-validation-20110523.patch
> 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
> Attachments: config-validation-20110523.patch
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
