Right, that's perfectly appropriate. Feel free to attach unfinished
versions of the patch! Just comment that it's not finished and
people may have time to take a look at what you've done so far
and make comments. Sometimes this saves you from a whole
bunch of work :)...
Best,
Erick
On Wed, Mar 5,
Hi Erick
The patch is in progress. Looking at the code I can't figure out why this
restriction was added I'll create a jira issue and post.
Thanks for your help
Regards
Sent from my iPhone
> On 5 Mar 2014, at 20:36, Erick Erickson wrote:
>
> Well, if you're going to go that route, how abou
Well, if you're going to go that route, how about developing
a patch for QEV? Of course there may be a very good reason
it wasn't done there, I haven't looked at the code
Best,
Erick
On Mon, Mar 3, 2014 at 1:07 PM, David Stuart wrote:
> HI Erick,
>
> Thanks for the response.
> On the wiki it
HI Erick,
Thanks for the response.
On the wiki it states
config-file
Path to the file that defines query elevation. This file must exist in
$/conf/ or$/.
If the file exists in the /conf/ directory it will be loaded once at startup.
If it exists in the data directory, it will be reloaded for
Hmmm, you _ought_ to be able to specify a relative path
in solrconfig_slave.xml:solrconfig.xml,x.xml,y.xml
But there's certainly the chance that this is hard-coded in
the query elevation component so I can't say that this'll work
with assurance.
Best,
Erick
On Sun, Mar 2, 2014 at 6:14 AM, David
Hi sorry for the cross post but I got no response in the dev group so assumed I
posted in the wrong place.
I am using Solr 3.6 and am trying to automate the deployment of cores with a
custom elevate file. It is proving to be difficult as most of the file (schema,
stop words etc) support absol
