Re: Dynamically loaded core.properties file

2014-08-21 Thread Erick Erickson
Ryan: A slight misunderstanding here: The idea of allowing different names for the core.properties file was the "can of worms". Or at least a new can of worms. Using the existing stuff is an existing can of worms ;)... Under any circumstances the only time this would come in to play is if you are

Re: Dynamically loaded core.properties file

2014-08-21 Thread Ryan Josal
Thanks Erick, I tested that does work, and provide a solution to my problem! So property expansion does work in core.properties, I did not know that, and I got the impression from Chris' comment that that would open up a can of worms when it comes to persisting core.properties. I guess while

Re: Dynamically loaded core.properties file

2014-08-20 Thread Umesh Prasad
The core discovery process is dependent on presence of core.properties file in the particular directory. You can have a script, which will traverse the directory structure of core base directory and depending on env/host name, will either restore core.properties or rename it to a different file.

Re: Dynamically loaded core.properties file

2014-08-20 Thread Erick Erickson
OK, not quite sure if this would work, but In each core.properties file, put in a line similar to what Chris suggested: properties=${env}/custom.properties You might be able to now define your sys var like -Drelative_or_absolute_path_to_dev_custom.proerties file. or -Drelative_or_absolute_pat

Re: Dynamically loaded core.properties file

2014-08-20 Thread Ryan Josal
Thanks Erick, that mirrors my thoughts exactly. If core.properties had property expansion it would work for this, but I agree with not supporting that for the complexities it introduces, and I'm not sure it's the right way to solve it anyway. So, it doesn't really handle my problem. I think

Re: Dynamically loaded core.properties file

2014-08-20 Thread Erick Erickson
Hmmm, I was going to make a code change to do this, but Chris Hostetter saved me from the madness that ensues. Here's his comment on the JIRA that I did open (but then closed), does this handle your problem? I don't think we want to make the name of core.properties be variable ... that way leads t

Dynamically loaded core.properties file

2014-08-20 Thread Ryan Josal
Hi all, I have a question about dynamically loading a core properties file with the new core discovery method of defining cores. The concept is that I can have a dev.properties file and a prod.properties file, and specify which one to load with -Dsolr.env=dev. This way I can have one file whi