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

Yusuke Yanbe updated SOLR-3149:
-------------------------------

    Affects Version/s: 4.0
    
> Update obsolete schema.xml in example-DIH
> -----------------------------------------
>
>                 Key: SOLR-3149
>                 URL: https://issues.apache.org/jira/browse/SOLR-3149
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>    Affects Versions: 3.5, 4.0
>            Reporter: Yusuke Yanbe
>            Priority: Minor
>              Labels: dataimportHandler, documentaion, newbie
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> The version of example/example-DIH/solr/db/conf/schema.xml is 1.1 (too old) 
> where example/solr/conf/schema.xml is 1.4. I believe that it is important to 
> keep all schema.xml up to date for newbies.
> The example/example-DIH/solr/db/conf/schema.xml will be referred as primary 
> hints for newbies because most of them may want to try import some data from 
> their preexisting DB or something first, referring [1]. Even 
> DataImportHandler tutorial itself can be done without problem, obsolete 
> schema.xml may confusing for them. 
> Typical difference of new and old schema.xml is existence of explanation of 
> *TrieField. Because old one's default types are solr.IntField or 
> solr.DateField and no mention of this. Consequently, when they try range 
> queries or boosting query based on old schema.xml, they may face unintended 
> slow response or error.
> [1] http://wiki.apache.org/solr/DataImportHandler#Full_Import_Example

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to