Hi:
Use Raw Query Parameters to pass in an array. How can you use cursors to refer
to elements of an array in a function?
For example，How do I get $a[0] to work properly：
"params":{
"a":["1”, "2”, "3"],
"q": "*:*",
"fl": "$a, $a[0]"
}
Thank you very much
ses (which are not necessary at
> > all).
> >
> > What exactly are you expecting?
> >
> > -Michael
> >
> > Am 24.04.2017 um 12:59 schrieb VJ:
> >> Hi All,
> >>
> >> I am facing issues with OR/AND conditions with query parameters:
> >>
outside the parenthesises (which are not necessary at
> all).
>
> What exactly are you expecting?
>
> -Michael
>
> Am 24.04.2017 um 12:59 schrieb VJ:
>> Hi All,
>>
>> I am facing issues with OR/AND conditions with query parameters:
>>
>> fq=ciona
Hi All,
>
> I am facing issues with OR/AND conditions with query parameters:
>
> fq=cioname:"XYZ" & (fq=attr1:trueORattr2:true)
>
> The queries are not returning expected results.
>
> I have tried various permutation and combinations but couldn't get it
> working. Any pointers on this?
>
>
>
> Regards,
> VJ
>
Hi All,
I am facing issues with OR/AND conditions with query parameters:
fq=cioname:"XYZ" & (fq=attr1:trueORattr2:true)
The queries are not returning expected results.
I have tried various permutation and combinations but couldn't get it
working. Any pointers on this?
Regards,
VJ
meters in the gateway for
simplicity and security issues (e.g. Shortening the size of HTTP call, Prevent
db names, field names, etc. shown in the HTTP call, etc.)
And these considerations ended up with a gateway design.
For your question, IMHO, I wouldn't define query parameters in Solr unless
estion, IMHO, I wouldn't define query parameters in Solr unless you
think they WOULD BE GLOBALIZED. You can consider our solution.
scott.chu，scott@udngroup.com
2016/6/15 (週三)
- Original Message -
From: Derek Poh
To: solr-user
CC:
Date: 2016/6/13 (週一) 11:21
Subject: Define s
Hi Emir
Yaguess one way is to implement a policy where new queries from client
application have to be reviewcouple with periodic search log grooming as
you have suggested.
On 6/14/2016 4:12 PM, Emir Arnautovic wrote:
Hi Derek,
Unless you lock all your parameters, there will always be a chanc
Hi Derek,
Unless you lock all your parameters, there will always be a chance of
inefficient queries. Only way to fight that is to have full control of
Solr interface and provide some search API, or to do regular search log
grooming.
Emir
On 14.06.2016 03:05, Derek Poh wrote:
Hi Emir
Thank
Hi Emir
Thank you for pointing out the cons of defining them in Solr config.
One of the thing I am worry about in letting clientapplication defined
the parametersis the developers will use or include unnecessary, wrong
and resource intensive parameters.
On 6/13/2016 5:50 PM, Emir Arnautovic
Hi Derek,
Maybe I am looking this from perspective who is working with other
peoples' setups, but I prefer when it is defined in Solr configs: I can
get sense of queries from looking at configs, you have mechanism to lock
some parameters, updates are centralized... However, it does come with
s
Hi
Would like to get some advice on should the queries parameters be define
in Solr or let the clients applications define and pass the queries
parameters to Solr?
Regards,
Derek
--
CONFIDENTIALITY NOTICE
This e-mail (including any attachments) may contain confidentia
Hi Mark,
Try using set method instead of add method : params1.set("fl", "id");
I also suggest to use static String for "fl" as you used CommonParams.Q for "q"
Congrats for your first search component!
happy searching,
Ahmet
On Saturday, January 9, 2016 11:32 PM, Mark Robinson
wrote:
Th
Thanks Eric!
Appreciate your valuable suggestions.
Now I am getting the concept of a search-component better!
So my custom class is just this after removing the SOLRJ part, as I just
need to modify the query by adding some parameters dynamically before the
query actually is executed by SOLR:-
pu
Woah, Mark…. you’re making a search request within a search component.
Instead, let the built-in “query” component do the work for you.
I think one fix for you is to make your “components” be “first-components”
instead (allowing the other default search components to come into play). You
don
Hi,
Ahmet, Jack, Thanks for the pointers.
My requirement is, I would not be having the facets or sort fields or its
order as static.
For example suppose for a particular scenario I need to show only 2 facets
and sort on only one field.
For another scenario I may have to do facet.field for a differ
Sure, you CAN do this, but why would you want to? I mean, what exactly is
the motivation here? If you truly have custom code to execute, fine, but if
all you are trying to do is set parameters, a custom request handler is
hitting a tack with a sledge hammer. For example, why isn't setting
defaults
Hi Mark,
Yes this is possible. Better, you can use a custom SearchComponent for this
task too.
You retrieve solr parameters, wrap it into ModifiableSolrParams. Add extra
parameters etc, then pass it to underlying search components.
Ahmet
On Saturday, January 9, 2016 3:59 PM, Mark Robinson
w
Hi,
When I initially fire a query against my Solr instance using SOLRJ I pass
only, say q=*:*&fq=(myfield:vaue1).
I have written a custom RequestHandler, which is what I call in my SolrJ
query.
Inside this custom request handler can I add more query params like say the
facets etc.. so that ultimat
Whew! I was afraid that my memory was failing since I'd no memory of
ever seeing anything remotely like that!
Erick
On Thu, Mar 5, 2015 at 6:04 AM, wrote:
> Please ignore my question.
>
> These are form field names which I created a couple of months ago, not SOLR
>
Please ignore my question.
These are form field names which I created a couple of months ago, not SOLR
query parameters.
Philippe
- Mail original -
De: phi...@free.fr
À: solr-user@lucene.apache.org
Envoyé: Jeudi 5 Mars 2015 14:54:26
Objet: SOLR query parameters
Hello,
could someone
Hello,
could someone please explain what these SOLR query parameter keywords stand for:
- ppcdb
- srbycb
- as
For instance,
http://searcharchives.iht.com:8983/solr/inytapdf0/browse?ppdcb=&srbycb=&as=&q=kaiser&sort=
I could not find them in the SOLR documentation.
Many thanks.
Philippe
You saved my life Shawn! Thanks!
On Mon, Apr 28, 2014 at 11:54 PM, Shawn Heisey wrote:
> On 4/28/2014 7:54 PM, Xavier Morera wrote:
> > Would anyone be so kind to explain what are the "Raw query parameters"
> > in Solr's admin UI. I can't find an explanatio
On 4/28/2014 7:54 PM, Xavier Morera wrote:
> Would anyone be so kind to explain what are the "Raw query parameters"
> in Solr's admin UI. I can't find an explanation in either the reference
> guide nor wiki nor web search.
The query API supports a lot more parameter
Hi,
Would anyone be so kind to explain what are the "Raw query parameters" in
Solr's admin UI. I can't find an explanation in either the reference guide
nor wiki nor web search.
[image: Inline image 1]
A bit confused on what it actually is for
[image: Inline image 3]
Thank
ions entry. these fields are
>> multivalued.
>>
>> -----Original-Nachricht-
>> > Von: "Erick Erickson"
>> > An: solr-user@lucene.apache.org
>> > Datum: 19/02/2014 04:09
>> > Betreff: Re: query parameters
>> >
>> > Solr/Luce
d all docs without organisations and roles or
> those that have at least one roles and organisations entry. these fields
> are multivalued.
>
> -Original-Nachricht-
> > Von: "Erick Erickson"
> > An: solr-user@lucene.apache.org
> > Datum: 19/02/20
t; Von: "Erick Erickson"
> An: solr-user@lucene.apache.org
> Datum: 19/02/2014 04:09
> Betreff: Re: query parameters
>
> Solr/Lucene query language is NOT strictly boolean, see
> Chris's excellent blog here:
> http://searchhub.org/dev/2011/12/28/why-not-and-or-
> value
> in ogranisations and roles. It didn't matter if i used a base term, isn't
> that give through the q-parameter?
>
> -Original Message-
> From: Raymond Wiker [mailto:rwi...@gmail.com]
> Sent: Dienstag, 18. Februar 2014 13:19
> To: solr-user@lucene.
ar 2014 13:19
To: solr-user@lucene.apache.org
Subject: Re: query parameters
That could be because the second condition does not do what you think it
does... have you tried running the second condition separately?
You may have to add a "base term" to the second condition, like what
TO *]) only
> returns docs that match the first conditions. it doesn't return any docs
> with the empty fields organisations and roles.
>
> -Original Message-
> From: Andreas Owen [mailto:a...@conx.ch]
> Sent: Montag, 17. Februar 2014 05:08
> To: solr-user@luce
roles.
-Original Message-
From: Andreas Owen [mailto:a...@conx.ch]
Sent: Montag, 17. Februar 2014 05:08
To: solr-user@lucene.apache.org
Subject: query parameters
in solrconfig of my solr 4.3 i have a userdefined requestHandler. i would like
to use fq to force the following conditions:
1: or
in solrconfig of my solr 4.3 i have a userdefined requestHandler. i would like
to use fq to force the following conditions:
1: organisations is empty and roles is empty
2: organisations contains one of the commadelimited list in variable $org
3: roles contains one of the commadelimited l
mp;facet.field=inputmethod&wt=json&indent=true
>
> Thanks, Deepak
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Facet-in-query-parameters-return-all-the-fields-instead-of-the-field-mentioned-in-facet-field-paramer-tp4108884.html
> Sent fr
rhost:8983/solr/collection1/select?q=event_date:2013-12-19&facet=true&facet.field=inputmethod&wt=json&indent=true
Thanks, Deepak
--
View this message in context:
http://lucene.472066.n3.nabble.com/Facet-in-query-parameters-return-all-the-fields-instead-of-the-field-mentioned-in-fac
: when disabling the facet, the query works perfectly. I understand that
: either defType parameter or q.myalias.qf parameters, do not affect the
: facet query (which always runs with lucene parser??)
a top level defType param only applies to the "q" param. This is by
design.
"defType" is sp
lias is OK or edismax "recovery mode" is too much
"nice". debugQuery does not show the parsedQuery for facet query.
Anyway, there is a problem here.
On Tue, Dec 10, 2013 at 3:09 AM, Chris Hostetter
wrote:
> : It seems that a facet query does not use the global query par
: It seems that a facet query does not use the global query parameters (for
: example, field aliasing for edismax parser).
can you please give a specific example of a query that isn't working for
you?
Using this query against the examle data, things work exactly as i would
expect showing
created SOLR-5542.
Anyone else want it?
On Thu, Dec 5, 2013 at 8:55 PM, Isaac Hebsh wrote:
> Hi,
>
> It seems that a facet query does not use the global query parameters (for
> example, field aliasing for edismax parser).
> We have an intensive use of facet queries (in some c
Hi,
It seems that a facet query does not use the global query parameters (for
example, field aliasing for edismax parser).
We have an intensive use of facet queries (in some cases, we have a lot of
facet.query for a single q), and the using of LocalParams for each
facet.query is not convenient
fault operator to AND
> somewhere.
>
> search results will contain all categories, but 206 will be boosted.
>
--
View this message in context:
http://lucene.472066.n3.nabble.com/how-to-boost-given-word-in-a-field-in-the-query-parameters-tp4003961p4004061.html
Sent from the Solr - User mailing list archive at Nabble.com.
> search results will contain all categories, but 206 will be boosted.
>
--
View this message in context:
http://lucene.472066.n3.nabble.com/how-to-boost-given-word-in-a-field-in-the-query-parameters-tp4003961p4004057.html
Sent from the Solr - User mailing list archive at Nabble.com.
> Thanks for your reply, if I insert the clause
> category:206^100 , the search
> result will only include the results in category 206
> ?
It will be an optional clause, unless you have set default operator to AND
somewhere.
search results will contain all categories, but 206 will be boosted.
206 is in front of others*
>
> One way to do this is : add a clause into your query.
>
> q=cell phone category:206^100
>
--
View this message in context:
http://lucene.472066.n3.nabble.com/how-to-boost-given-word-in-a-field-in-the-query-parameters-tp4003961p4003981.html
Sent from the Solr - User mailing list archive at Nabble.com.
> category field has certain values ,for
> examples:307,503,206..
>
> my query like
> this:q=cell+phone&version=2.2&start=0&rows=10&indent=on
> the search result will be in many categories ,for example
> may be in
> 206,782,307,289
> you know the the default sort which depends on the
> relevance,
this message in context:
http://lucene.472066.n3.nabble.com/how-to-boost-given-word-in-a-field-in-the-query-parameters-tp4003961.html
Sent from the Solr - User mailing list archive at Nabble.com.
:
http://localhost:8983/solr/core0/select?q={!join%20from=matchset_id_ss%20to=id}*:*&fq=status_s:completed
:
: I get filtered results of documents that are completed. The issue I am now
: trying to face is how do I filter the initial search of documents based on
: multiple conditions and then ge
Hi all,
I am trying to use the Join feature in SOLR trunk with limited sucess. I
am able to make simple searches and get the returns of documents as
expected. A query such a follows works perfectly fine and as expected:
http://localhost:8983/solr/core0/select?q={!join%20from=matchset_id_ss%
n, where as map only
accepts constants. So if I rephrase my requirements, it would be:
1. Calculate score for each document using query parameters(search
parameters)
2. Sort these documents based on score
So I know that I can change default scoring by overriding DefaultSimilarity
class, but how
, Michael Moores wrote:
> Trying to answer my own question.. seems like it would be a good idea to
> create a SearchComponent and add this to the list of existing components.
> My component just converts query parameters to something that the solr
> QueryComponent understands.
> One good
Trying to answer my own question.. seems like it would be a good idea to create
a SearchComponent and add this to the list of existing components.
My component just converts query parameters to something that the solr
QueryComponent understands.
One good way of doing it?
On Feb 23, 2011, at 8
I'm required to provide a handler with some specialized query string inputs.
I'd like to translate the query inputs to a lucene/solr query and delegate the
request to the existing lucene/dismax handler.
What's the best way to do this?
Do I implement SolrRequestHandler, or a QParser? Do I extend
You can mix and match all sorts of things with Solr's flexible query
parsing capabilities.
See the great blog entry by Yonik here:
http://www.lucidimagination.com/blog/2009/03/31/nested-queries-in-solr/
Erik
On Jan 8, 2010, at 5:30 AM, Oliver Beattie wrote:
Can anyone help me out
Can anyone help me out with this? It'd be really appreciated :)
2010/1/7 Oliver Beattie
> Hey,
>
> I'm doing a query which involves using an frange in the filter query — and
> I was wondering if there is a way of combing the frange with other
> parameters. Something like ({!frange l=x u=y)*do st
On Jan 7, 2010, at 1:05 PM, Jon Poulton wrote:
I've also just noticed that QueryParsing is not in the SolrJ API.
It's in one of the other Solr jar dependencies.
I'm beginning to think that maybe the best approach it to write a
query string generator which can generate strings of the form:
> Using SolrQuery.setQuery("{!lucene q.op=AND
> df=text}myfield:foo +bar -baz}"); would make more sense if
> it were not for the other methods available on SolrQuery.
>
> For example, there is a "setFields(String..)" method. So
> what happens if I call setFields("title", "description")
> after ha
ubject: Re: SolJ and query parameters
--- On Thu, 1/7/10, Jon Poulton wrote:
> From: Jon Poulton
> Subject: SolJ and query parameters
> To: "'solr-user@lucene.apache.org'"
> Date: Thursday, January 7, 2010, 7:25 PM
> Hi there,
> I'm trying to unde
Cheers
Jon
-Original Message-
From: Ahmet Arslan [mailto:iori...@yahoo.com]
Sent: 07 January 2010 17:38
To: solr-user@lucene.apache.org
Subject: Re: SolJ and query parameters
--- On Thu, 1/7/10, Jon Poulton wrote:
> From: Jon Poulton
> Subject: SolJ and query parameters
>
--- On Thu, 1/7/10, Jon Poulton wrote:
> From: Jon Poulton
> Subject: SolJ and query parameters
> To: "'solr-user@lucene.apache.org'"
> Date: Thursday, January 7, 2010, 7:25 PM
> Hi there,
> I'm trying to understand how the query syntax specified
Hi there,
I'm trying to understand how the query syntax specified on the Solr Wiki (
http://wiki.apache.org/solr/SolrQuerySyntax ) fits in with the usage of the
SolJ class SolrQuery. There are not too many examples of usage to be found.
For example. Say I wanted to replicate the following query
Hey,
I'm doing a query which involves using an frange in the filter query — and I
was wondering if there is a way of combing the frange with other parameters.
Something like ({!frange l=x u=y)*do stuff*) AND *field:param*) — but
obviously this doesn't work. Is there a way of doing this?
—Oliver
735009/result.xml result.xml
> --
> View this message in context:
> http://www.nabble.com/Incorrect-sort-with-with-function-query-in-query-parameters-tp22735009p22735009.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
I have been intending to although I have been dragging my feet on it. I've
never opened a bug before so I'm not sure of the protocol. If you don't
mind, it would be great if you could send me a pm and point me in the right
direction.
Thanks,
Asif
On Mon, May 18, 2009 at 7:30 PM, Ensdorf Ken
>
> A Unit test would be ideal, but even if you can just provide a list of
> steps (ie: using this solrconfig+schema, index these docs, then update
> this one doc, then execute this search) it can help people track things
> down.
>
> Please open a bug and attach as much detail as you can there.
>
>
: Any documents marked deleted in this index are just the result of updates to
: those documents. There are no purely deleted documents. Furthermore, the
: field that I am ordering by in my function query remains untouched over the
: updates.
it doesn't matter wether it was an update or a true
in context:
http://www.nabble.com/Incorrect-sort-with-with-function-query-in-query-parameters-tp22735009p22741058.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Asif Rahman
> To: solr-user@lucene.apache.org
> Sent: Thursday, March 26, 2009 10:24:19 PM
> Subject: Incorrect sort with with function query in query parameters
>
>
> Hi al
View this message in context:
http://www.nabble.com/Incorrect-sort-with-with-function-query-in-query-parameters-tp22735009p22735009.html
Sent from the Solr - User mailing list archive at Nabble.com.
68 matches
Mail list logo
