Re: q.op in 7.2.1 solconfig.xml

2018-02-21 Thread Emir Arnautović
You are welcome!
In case you want to prevent overrides, you can put it in invariants section.

Emir

On Feb 22, 2018 12:32 AM, "Peter Sturge"  wrote:

> Hi,
> Thanks for your reply.
>
> I managed to get it working by specifying it in the requestHandler /select
> section in solrconfig.xml:
>   
> 
> 
>   explicit
>   10
>   AND
> 
>   
>
> Your other suggestions will be also useful for everyone with a similar
> question. Thanks!
>
> Peter
>
>
>
> On Wed, Feb 21, 2018 at 11:22 PM, Emir Arnautović <
> emir.arnauto...@sematext.com> wrote:
>
> > Hi Peter,
> > You should be able to set any param in several places/ways:
> > * define in request handler defaults
> > * define in params.json and reference using useParams in request handler
> > definition
> > * use initParams to define default for one or multiple handlers
> >
> > You can see examples in configs that are part of Solr installation.
> >
> > HTH,
> > Emir
> > --
> > Monitoring - Log Management - Alerting - Anomaly Detection
> > Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> >
> >
> >
> > > On 21 Feb 2018, at 23:27, Peter Sturge  wrote:
> > >
> > > Hi,
> > > I'm going through a major upgrade from 4.6 to 7.2.1 and I can see the
> > > defaultOperator has now been removed.
> > >
> > > The docs mention it's possible to set a default value for the new q.op
> > > directive in solrconfig.xml, but it doesn't say how or where.
> > >
> > > Does anyone have an example of specifying a default q.op parameter?
> > Really
> > > don't want to have to include it in *every* query, that kinda defeats
> its
> > > purpose...
> > >
> > > Thanks,
> > > Peter
> >
> >
>


Re: q.op in 7.2.1 solconfig.xml

2018-02-21 Thread Peter Sturge
Hi,
Thanks for your reply.

I managed to get it working by specifying it in the requestHandler /select
section in solrconfig.xml:
  


  explicit
  10
  AND

  

Your other suggestions will be also useful for everyone with a similar
question. Thanks!

Peter



On Wed, Feb 21, 2018 at 11:22 PM, Emir Arnautović <
emir.arnauto...@sematext.com> wrote:

> Hi Peter,
> You should be able to set any param in several places/ways:
> * define in request handler defaults
> * define in params.json and reference using useParams in request handler
> definition
> * use initParams to define default for one or multiple handlers
>
> You can see examples in configs that are part of Solr installation.
>
> HTH,
> Emir
> --
> Monitoring - Log Management - Alerting - Anomaly Detection
> Solr & Elasticsearch Consulting Support Training - http://sematext.com/
>
>
>
> > On 21 Feb 2018, at 23:27, Peter Sturge  wrote:
> >
> > Hi,
> > I'm going through a major upgrade from 4.6 to 7.2.1 and I can see the
> > defaultOperator has now been removed.
> >
> > The docs mention it's possible to set a default value for the new q.op
> > directive in solrconfig.xml, but it doesn't say how or where.
> >
> > Does anyone have an example of specifying a default q.op parameter?
> Really
> > don't want to have to include it in *every* query, that kinda defeats its
> > purpose...
> >
> > Thanks,
> > Peter
>
>


Re: q.op in 7.2.1 solconfig.xml

2018-02-21 Thread Emir Arnautović
Hi Peter,
You should be able to set any param in several places/ways:
* define in request handler defaults
* define in params.json and reference using useParams in request handler 
definition
* use initParams to define default for one or multiple handlers

You can see examples in configs that are part of Solr installation.

HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/



> On 21 Feb 2018, at 23:27, Peter Sturge  wrote:
> 
> Hi,
> I'm going through a major upgrade from 4.6 to 7.2.1 and I can see the
> defaultOperator has now been removed.
> 
> The docs mention it's possible to set a default value for the new q.op
> directive in solrconfig.xml, but it doesn't say how or where.
> 
> Does anyone have an example of specifying a default q.op parameter? Really
> don't want to have to include it in *every* query, that kinda defeats its
> purpose...
> 
> Thanks,
> Peter