[ 
https://issues.apache.org/jira/browse/SOLR-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl updated SOLR-1758:
------------------------------

          Component/s:     (was: contrib - DataImportHandler)
          Description: 
It is too easy to make configuration errors in Solr without getting warnings. 
We should explore ways of validation configurations. See mailing list 
discussion at http://search-lucene.com/m/h6xKf1EShE6


  was:
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



    Affects Version/s:     (was: 1.4)
        Fix Version/s: 4.0
               Labels: configuration schema.xml solrconfig.xml validation xsd  
(was: )
              Summary: schema definition for configuration files (validation, 
XSD)  (was: schema definition for configuration files)

Original Description by Jorg Heymans:

{quote}
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
{quote}
                
> schema definition for configuration files (validation, XSD)
> -----------------------------------------------------------
>
>                 Key: SOLR-1758
>                 URL: https://issues.apache.org/jira/browse/SOLR-1758
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Jorg Heymans
>              Labels: configuration, schema.xml, solrconfig.xml, validation, 
> xsd
>             Fix For: 4.0
>
>         Attachments: config-validation-20110523.patch
>
>
> It is too easy to make configuration errors in Solr without getting warnings. 
> We should explore ways of validation configurations. See mailing list 
> discussion at http://search-lucene.com/m/h6xKf1EShE6

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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

Reply via email to