You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Terrance A. Snyder (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/03/14 17:08:40 UTC
[jira] [Issue Comment Edited] (SOLR-1970) need to customize
location of dataimport.properties
[ https://issues.apache.org/jira/browse/SOLR-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229289#comment-13229289 ]
Terrance A. Snyder edited comment on SOLR-1970 at 3/14/12 4:08 PM:
-------------------------------------------------------------------
+1 I am looking at implementing with current trunk. I'll hopefully submit a patch to this. Keep in mind this may have to be added to the core configuration area to keep backward compatibility.
Something like:
<core name="users_001" instanceDir="users" config="solrconfig.xml" dataDir="../users_001" dataImportPropertiesFile="../users_001/di.properties"/>
<core name="users_002" instanceDir="users" config="solrconfig.xml" dataDir="../users_002" dataImportPropertiesFile="../users_002/di.properties"/>
This would operation just like todays core config:
$SOLR_HOME/users
/users/conf
/users/conf/solrconfig.xml
/users/conf/schema.xml
/users_001
/users_001/data
/users_001/di.properties
/users_002
/users_002/data
/users_002/di.properties
This allows the core configuration and sharding to work effectively. The core question is how this would play with zookeeper / cloud support.
I would think this should already be baked into SolrCloud.... but I could be wrong. Any thoughts?
was (Author: terrance.snyder):
+1 I am looking at implementing with current trunk. I'll hopefully submit a patch to this. Keep in mind this may have to be added to the core configuration area to keep backward compatibility.
Something like:
<core name="users_001" instanceDir="users" config="solrconfig.xml" dataDir="../users_001" dataImportPropertiesFile="../users_001/di.properties"/>
<core name="users_002" instanceDir="users" config="solrconfig.xml" dataDir="../users_002" dataImportPropertiesFile="../users_001/di.properties"/>
This would operation just like todays core config:
$SOLR_HOME/users
/users/conf
/users/conf/solrconfig.xml
/users/conf/schema.xml
/users_001
/users_001/data
/users_001/di.properties
/users_002
/users_002/data
/users_002/di.properties
This allows the core configuration and sharding to work effectively. The core question is how this would play with zookeeper / cloud support.
I would think this should already be baked into SolrCloud.... but I could be wrong. Any thoughts?
> 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: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org