You haven't really told us what you tried and what the failure was.
Is your problem getting the _configuration_ created or using the
system variables after they're created?
You need to tell us exactly _what_ you tried and exactly _how_ what
you tried didn't work. Details matter, particularly what came through
the Solr log files.
If your problem is the using the config API to set up that section of
solrconfig.xml, let's see the exact command you used. I suspect an
escaping issue, but there's no data to go on.
Best,
Erick
On Fri, Jun 2, 2017 at 9:08 AM, Webster Homer <webster.ho...@sial.com> wrote:
> In the documentation for Solr cdcr there is an example of a source
> configuration that uses properties:
> <lst name="replica">
> <str name="zkHost">${TargetZk}</str>
> <str name="Source">${SourceCollection}</str>
> <str name="Target">${TargetCollection}</str>
> </lst>
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62687462#CrossDataCenterReplication(CDCR)-InitialStartup
>
> I tried to configure cdcr for a collection to use properties. It always
> failed. The only thing that seems to work is the literal strings for the
> Target Zookeeper, source and target collection names.
>
> I used the Solr Config API to create the properties, but it just didn't
> work. It was a while back but I believe all it did was throw errors.
>
> Is there some way to make this work? If not it should be removed from the
> documentation
>
> This seems like it would be a useful feature, especially since CDCR doesn't
> support the use of aliases, SOLR-10679.
>
> --
>
>
> This message and any attachment are confidential and may be privileged or
> otherwise protected from disclosure. If you are not the intended recipient,
> you must not copy this message or attachment or disclose the contents to
> any other person. If you have received this transmission in error, please
> notify the sender immediately and delete the message and any attachment
> from your system. Merck KGaA, Darmstadt, Germany and any of its
> subsidiaries do not accept liability for any omissions or errors in this
> message which may arise as a result of E-Mail-transmission or for damages
> resulting from any unauthorized changes of the content of this message and
> any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its
> subsidiaries do not guarantee that this message is free of viruses and does
> not accept liability for any damages caused by any virus transmitted
> therewith.
>
> Click http://www.emdgroup.com/disclaimer to access the German, French,
> Spanish and Portuguese versions of this disclaimer.
