[
https://issues.apache.org/jira/browse/SOLR-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049000#comment-13049000
]
C S commented on SOLR-2551:
---------------------------
I might be wrong but isn't the dataimport.properties written even if no
delta-query is configured? So even if you'd just be interested in full imports,
you'll run into an exception at the end of your full import when solr attempts
to write the timestamp into dataimport.properties.
However, if that's not the case (i.e. a non-writable dataimport.properties does
not break a full import), i'd suggest that the check if dataimport.properties
is writable should only be done if a delta-query is defined, and in this case
it should refuse to start the import.
> Checking dataimport.properties for write access during startup
> --------------------------------------------------------------
>
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
