[
https://issues.apache.org/jira/browse/SOLR-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063352#comment-13063352
]
Chris Male commented on SOLR-2551:
----------------------------------
Okay, so, given that basically every test writes to this file, what are our
options?
To me it seems since the file is getting written too (whether we rely on the
contents or not), this could get in the way of another test. So perhaps we need
to pull the checkWritablePersistFile method out for awhile and re-assess how to
achieve the same functionality in a way the tests can handle?
> Check dataimport.properties for write access before starting import
> -------------------------------------------------------------------
>
> Key: SOLR-2551
> URL: https://issues.apache.org/jira/browse/SOLR-2551
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Affects Versions: 1.4.1, 3.1
> Reporter: C S
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 3.3, 4.0
>
> Attachments: SOLR-2551.patch
>
>
> A common mistake is that the /conf (respectively the dataimport.properties)
> file is not writable for solr. It would be great if that were detected on
> starting a dataimport job.
> Currently and import might grind away for days and fail if it can't write its
> timestamp to the dataimport.properties file.
--
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
