[
https://issues.apache.org/jira/browse/SOLR-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-656:
------------------------------
Attachment: SOLR-656-rmdir.patch
New patch with completely different approach:
This time there are no unit tests. After doing everything it can to make sure
that a filesystem directory should exist, does exist, and contains nothing,
proceeds to remove that index directory and log a warning saying that it did so.
> better error message when "data/index" is completely empty
> ----------------------------------------------------------
>
> Key: SOLR-656
> URL: https://issues.apache.org/jira/browse/SOLR-656
> Project: Solr
> Issue Type: Wish
> Reporter: Hoss Man
> Fix For: 4.2, 5.0
>
> Attachments: SOLR-656.patch, SOLR-656-rmdir.patch
>
>
> Solr's normal behavior is to create an "index" dire in the dataDir if one
> does not already exist, but if "index" does exist it is used as is, warts and
> all ... if the index is corrupt in some way, and Solr can't create an
> IndexWriter or IndexReader that error is propagated up to the user.
> I don't think this should change: Solr shouldn't attempt to do anything
> special if there is a low level problem with the index, but something that
> i've seen happen more then a few times is that people unwittingly "rm
> index/*" when they should "run -r index" and as a result Solr+Lucene gives
> them an error instead of just giving them an empty index
> when checking if an existing index dir exists, it would probably be worth
> while to add a little one line sanity test that it contains some files, and
> log a warning.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
