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

Mikhail Khludnev updated SOLR-9725:
-----------------------------------
    Attachment: SOLR-9725.patch

Ok. Here we go. The earlier patch didn't lay smoothly. [~billnbell], 
[~jamiejackson], [~tinexw], please have a look to [^SOLR-9725.patch]. I see 
that properties are passed to resolveVariables(), but I'm not sure whether or 
not they are populated from the system's ones. 

> Allow Variables for All Data Import Handler Data Source Configuration Values
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-9725
>                 URL: https://issues.apache.org/jira/browse/SOLR-9725
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: contrib - DataImportHandler
>    Affects Versions: 5.5.3
>            Reporter: Jamie Jackson
>            Assignee: Mikhail Khludnev
>            Priority: Minor
>              Labels: patch
>         Attachments: SOLR-9725.patch
>
>
> I need to be able to use a variable for a password when also using 
> {{encryptKeyFile}}.
> For instance:
> {code:xml}
>       <dataSource
>               driver="${custom.dataimporter.datasource.driver}"
>               url="${custom.dataimporter.datasource.url}"
>               user="${custom.dataimporter.datasource.user}"
>               password="${custom.dataimporter.datasource.password}"
>               encryptKeyFile="/opt/solr/credentials/encrypt.key"
>       />
> {code}
> Because I need to change certain variables based on the environment. I'd 
> start like this:
> {code}
>      -a
>       -Dcustom.dataimporter.datasource.driver=org.mariadb.jdbc.Driver
>       
> -Dcustom.dataimporter.datasource.url=jdbc:mysql://local.mysite.com:3306/mysite
>       -Dcustom.dataimporter.datasource.user=root
>       
> -Dcustom.dataimporter.datasource.password=U2FsdGVkX1/dqwTb8RBfFq82SM37DkDRGeWMOndftHY=
> {code}
> If I hardcode the password, it works; if I use a variable reference, it 
> doesn't.
> As far as I know [this pull 
> request|https://github.com/apache/lucene-solr/pull/46] was submitted to 
> address this issue, but it didn't come with a Jira ticket or a full 
> explanation.
> Also, note that I'm not using a variable for the value of {{encryptKeyFile}}, 
> because [it's not possible in 5.x, though it seems to be fixed in 
> 6.1|https://issues.apache.org/jira/browse/SOLR-8610]. Presumably, the above 
> patch would encompass {{encryptKeyFile}}'s value, as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to