[ 
https://issues.apache.org/jira/browse/SOLR-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexandre Rafalovitch resolved SOLR-13540.
------------------------------------------
    Resolution: Invalid

This is not a correct usage of issue tracker for Solr project. We use it to 
track bugs and issues.

The correct location for this question is Solr Users mailing list. Especially 
because what you are asking is possible in several different ways and worth a 
discussion.

In short points:
* DIH is no longer recommended for the production environments (never really 
was)
* You can pass environmental variables into most of Solr and you can define 
those IIRC on command line, in solrconfig.xml or in core.properties
* You may also be able to use JDBC pools and use Java standard ways to separate 
environments for that (this may or may not work with recent Solr versions, due 
to bundling of Jetty)

> Is it possible configure a single data-config.xml file for all the 
> environments?
> --------------------------------------------------------------------------------
>
>                 Key: SOLR-13540
>                 URL: https://issues.apache.org/jira/browse/SOLR-13540
>             Project: Solr
>          Issue Type: Wish
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 5.5.5
>            Reporter: Hugo Rodriguez
>            Priority: Major
>
> Hi
> I need to configure a single data-config.xml file in solr for SAS AML 7.1. I 
> have three environments: Development, quality and production, and you know 
> the first lines in a data-config.xml file is for connection to a database 
> (database name, database server, port, user, password, etc). According to 
> this, is it possible to configure only one file (data.config.xml) that 
> dinamically connects for each of the databases in all environments?
> Thanks for all your answers
> Best regards
> Hugo Rodriguez R



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to