[
https://issues.apache.org/jira/browse/SOLR-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493328#comment-13493328
]
Erik Andersson commented on SOLR-1970:
--------------------------------------
We just solved this issue by not using ${dataimporter.last_index_time} for
delta-imports. Instead we store the 'last_index_time' (one for each core) in a
DB table and use a sub-query to pull it out.
SELECT
...
WHERE
date_modified > (SELECT `value` FROM `meta` WHERE
`key`='solr.dataimporter.last_index_time')
We run delta imports from a script so we can simply update the
'last_index_time' in that process (add a sleep() to make sure delta kicks in
before the 'last_index_time' is updated). I'm sure there are better solutions
that could trigger the update within Solr.
> need to customize location of dataimport.properties
> ---------------------------------------------------
>
> Key: SOLR-1970
> URL: https://issues.apache.org/jira/browse/SOLR-1970
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
> Affects Versions: 1.4
> Reporter: Chris Book
>
> By default dataimport.properties is written to {solr.home}/conf/. However
> when using multiple solr cores, it is currently useful to use the same conf
> directory for all of the cores and use solr.xml to specify a different
> schema.xml. I can then specify a different data-config.xml for each core to
> define how the data gets from the database to each core's shema.
> However, all the solr cores will fight over writing to the
> dataimport.properties file. There should be an option in solrconfig.xml to
> specify the location or name of this file so that a different one can be used
> for each core.
--
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]
