Re: Memory Usage increases by a lot during and after optimization .
On 12/31/2015 8:03 PM, Zheng Lin Edwin Yeo wrote: > But the problem I'm facing now is that during optimizing, the memory usage > of the server hit the maximum of 64GB, and I believe the optimization could > not be completed fully as there is not enough memory, so when I check the > index again, it says that it is not optimized. Before the optimization, the > memory usage was less than 16GB, so the optimization actually uses up more > than 48GB of memory. > > Is it normal for an index size of 200GB to use up so much memory during > optimization? What *exactly* are you looking at that says Solr is using all your memory? You must be extremely specific when answering this question. This will determine whether we should be looking for a bug or not. It is completely normal for all modern operating systems to use all the memory when the amount of data being handled is large. Some of the memory will be allocated to programs like Java/Solr, and the operating system will use everything else to cache data from I/O operations on the disk. This is called the page cache. For Solr to perform well, the page cache must be large enough to effectively cache your index data. https://en.wikipedia.org/wiki/Page_cache In another message thread, you indicated that your max heap was set to 14GB. Java will only ever use that much memory for the program that is being run, plus a relatively small amount so that Java itself can operate. Any significantly large resident memory allocation beyond the max heap would be an indication of a bug in Java, not a bug in Solr. With the index size at 200GB, I would hope to have at least 128GB of memory in the server, but I would *want* 256GB. 64GB may not be enough for good performance. Thanks, Shawn
Re: Issue with if() statement
Sample code for a simple query parser?
On Fri, Jan 1, 2016 at 3:08 PM, Upayavira wrote:
> You've got to think of what the queries will be that you produce under
> the bonnet - what you are talking about is either a (!func} or a
> {!frange} query - both of which are inefficient as they must scan the
> entire resultset.
>
> However, what you're trying to do is evaluate the length of the *input
> value*, not a value in the documents being searched, so this doesn't
> really apply - you're talking about doing some work before your query
> happens.
>
> Again, I'm not sure of a way to do this on a stock Solr, but with a
> little coding it should be achievable - you could extend the switch
> query parser, or you could write your own - they're not that hard to
> create. Or, you could create a search component that operates before the
> QueryComponent does.
>
> A simple queryparser of your own would seem like a pretty lightweight
> thing - probably 20 lines of code or less.
>
> Upayavira
>
> On Fri, Jan 1, 2016, at 09:40 PM, William Bell wrote:
> > Forgot last bit:
> >
> > fq={!switch case.gt.0=$state1
> > default=$state
> > func=len($state1)}
> >
> >
> > On Fri, Jan 1, 2016 at 2:39 PM, William Bell
> wrote:
> >
> > > Maybe we can add function value on a switch?
> > >
> > > fq={!switch case.gt.0
> > > default=$state
> > > func=len($state1)}
> > >
> > >
> > >
> > > We could add: gt, lt, eq, ge, le ?
> > >
> > > gt: greater than
> > > lt: less than
> > > eq: equal
> > > ge: greater than or equal
> > > le: less than or equal
> > >
> > > ??
> > >
> > >
> > >
> > > On Fri, Jan 1, 2016 at 2:25 PM, William Bell
> wrote:
> > >
> > >> This all started with me trying to use {!switch} to indicate with CO
> or
> > >> NY to use. if we pass state1, that is supposed to take precedence,
> but if
> > >> nothing is returned, then use state Make sense now?
> > >>
> > >> I could not find a way to check for strlen($state1). Which is what I
> want
> > >> in the case statement. This just does not work...
> > >> Something like the following is what I am trying to do:
> > >>
> > >>
> > >> fq={!switch case."anything"=$state1
> > >> default=$state
> > >> v=$state1}
> > >>
> > >> So I tried the following to set all 50 states:
> > >>
> > >>
> > >> fq={!switch case.all='*:*'
> > >> case.CO='state:CO'
> > >> case.NY='state:NY'
> > >> v=$state1}
> > >>
> > >>
> > >> Obviously Oregon (OR!) is an issue, and it won't work at all plus
> > >>
> > >>
> > >>
> > >> On Fri, Jan 1, 2016 at 2:15 PM, William Bell
> wrote:
> > >>
> > >>> Another weirdness:
> > >>>
> > >>>
> > >>>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
> > >>> <
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq=%7B!lucene%20v=$tt%7D
> >
> > >>>
> > >>> That does not return anything.
> > >>>
> > >>> But if I set v=$state1 I get results.
> > >>>
> > >>> Can I not set equivalent variables?
> > >>>
> > >>>
> > >>>
> > >>> On Fri, Jan 1, 2016 at 2:07 PM, William Bell
> > >>> wrote:
> > >>>
> > Example.
> >
> >
> >
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
> > <
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state1%7D
> >
> >
> > This return 236,000
> >
> >
> >
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
> > <
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq=%7B!lucene%20v=$state%7D
> >
> >
> > This returns 10,000
> >
> > I want to put an IF statement around which v to use.
> >
> >
> >
> >
> >
> >
> > On Fri, Jan 1, 2016 at 1:52 PM, William Bell
> > wrote:
> >
> > > Sure.
> > >
> > > If the state:NY returns results filter by state:NY, if it does not,
> > > then use state:CO. If we have results in NY, use it, otherwise use
> CO.
> > >
> > > OK?
> > >
> > > On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
> > >
> > >>
> > >>
> > >> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> > >> > We are getting weird results with if(exists(a),b,c). We are
> getting
> > >> b+c!!
> > >> >
> > >> >
> > >>
> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state
Re: Issue with if() statement
You've got to think of what the queries will be that you produce under
the bonnet - what you are talking about is either a (!func} or a
{!frange} query - both of which are inefficient as they must scan the
entire resultset.
However, what you're trying to do is evaluate the length of the *input
value*, not a value in the documents being searched, so this doesn't
really apply - you're talking about doing some work before your query
happens.
Again, I'm not sure of a way to do this on a stock Solr, but with a
little coding it should be achievable - you could extend the switch
query parser, or you could write your own - they're not that hard to
create. Or, you could create a search component that operates before the
QueryComponent does.
A simple queryparser of your own would seem like a pretty lightweight
thing - probably 20 lines of code or less.
Upayavira
On Fri, Jan 1, 2016, at 09:40 PM, William Bell wrote:
> Forgot last bit:
>
> fq={!switch case.gt.0=$state1
> default=$state
> func=len($state1)}
>
>
> On Fri, Jan 1, 2016 at 2:39 PM, William Bell wrote:
>
> > Maybe we can add function value on a switch?
> >
> > fq={!switch case.gt.0
> > default=$state
> > func=len($state1)}
> >
> >
> >
> > We could add: gt, lt, eq, ge, le ?
> >
> > gt: greater than
> > lt: less than
> > eq: equal
> > ge: greater than or equal
> > le: less than or equal
> >
> > ??
> >
> >
> >
> > On Fri, Jan 1, 2016 at 2:25 PM, William Bell wrote:
> >
> >> This all started with me trying to use {!switch} to indicate with CO or
> >> NY to use. if we pass state1, that is supposed to take precedence, but if
> >> nothing is returned, then use state Make sense now?
> >>
> >> I could not find a way to check for strlen($state1). Which is what I want
> >> in the case statement. This just does not work...
> >> Something like the following is what I am trying to do:
> >>
> >>
> >> fq={!switch case."anything"=$state1
> >> default=$state
> >> v=$state1}
> >>
> >> So I tried the following to set all 50 states:
> >>
> >>
> >> fq={!switch case.all='*:*'
> >> case.CO='state:CO'
> >> case.NY='state:NY'
> >> v=$state1}
> >>
> >>
> >> Obviously Oregon (OR!) is an issue, and it won't work at all plus
> >>
> >>
> >>
> >> On Fri, Jan 1, 2016 at 2:15 PM, William Bell wrote:
> >>
> >>> Another weirdness:
> >>>
> >>>
> >>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
> >>>
> >>>
> >>> That does not return anything.
> >>>
> >>> But if I set v=$state1 I get results.
> >>>
> >>> Can I not set equivalent variables?
> >>>
> >>>
> >>>
> >>> On Fri, Jan 1, 2016 at 2:07 PM, William Bell
> >>> wrote:
> >>>
> Example.
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>
>
> This return 236,000
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>
>
> This returns 10,000
>
> I want to put an IF statement around which v to use.
>
>
>
>
>
>
> On Fri, Jan 1, 2016 at 1:52 PM, William Bell
> wrote:
>
> > Sure.
> >
> > If the state:NY returns results filter by state:NY, if it does not,
> > then use state:CO. If we have results in NY, use it, otherwise use CO.
> >
> > OK?
> >
> > On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
> >
> >>
> >>
> >> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> >> > We are getting weird results with if(exists(a),b,c). We are getting
> >> b+c!!
> >> >
> >> >
> >> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
> >>
> >> >
> >> > I am getting NY and CO!
> >> >
> >> > I only want $state1, which is NY.
> >> >
> >> > Any other ways to craft this?
>
Re: Issue with if() statement
Also ne: not equal.
This is like KSH.
On Fri, Jan 1, 2016 at 2:40 PM, William Bell wrote:
> Forgot last bit:
>
> fq={!switch case.gt.0=$state1
> default=$state
> func=len($state1)}
>
>
> On Fri, Jan 1, 2016 at 2:39 PM, William Bell wrote:
>
>> Maybe we can add function value on a switch?
>>
>> fq={!switch case.gt.0
>> default=$state
>> func=len($state1)}
>>
>>
>>
>> We could add: gt, lt, eq, ge, le ?
>>
>> gt: greater than
>> lt: less than
>> eq: equal
>> ge: greater than or equal
>> le: less than or equal
>>
>> ??
>>
>>
>>
>> On Fri, Jan 1, 2016 at 2:25 PM, William Bell wrote:
>>
>>> This all started with me trying to use {!switch} to indicate with CO or
>>> NY to use. if we pass state1, that is supposed to take precedence, but if
>>> nothing is returned, then use state Make sense now?
>>>
>>> I could not find a way to check for strlen($state1). Which is what I
>>> want in the case statement. This just does not work...
>>> Something like the following is what I am trying to do:
>>>
>>>
>>> fq={!switch case."anything"=$state1
>>> default=$state
>>> v=$state1}
>>>
>>> So I tried the following to set all 50 states:
>>>
>>>
>>> fq={!switch case.all='*:*'
>>> case.CO='state:CO'
>>> case.NY='state:NY'
>>> v=$state1}
>>>
>>>
>>> Obviously Oregon (OR!) is an issue, and it won't work at all plus
>>>
>>>
>>>
>>> On Fri, Jan 1, 2016 at 2:15 PM, William Bell
>>> wrote:
>>>
Another weirdness:
http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
That does not return anything.
But if I set v=$state1 I get results.
Can I not set equivalent variables?
On Fri, Jan 1, 2016 at 2:07 PM, William Bell
wrote:
> Example.
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>
>
> This return 236,000
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>
>
> This returns 10,000
>
> I want to put an IF statement around which v to use.
>
>
>
>
>
>
> On Fri, Jan 1, 2016 at 1:52 PM, William Bell
> wrote:
>
>> Sure.
>>
>> If the state:NY returns results filter by state:NY, if it does not,
>> then use state:CO. If we have results in NY, use it, otherwise use CO.
>>
>> OK?
>>
>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
>>
>>>
>>>
>>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>>> > We are getting weird results with if(exists(a),b,c). We are
>>> getting b+c!!
>>> >
>>> >
>>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>>>
>>> >
>>> > I am getting NY and CO!
>>> >
>>> > I only want $state1, which is NY.
>>> >
>>> > Any other ways to craft this?
>>>
>>> Does this work at all?
>>>
>>> The if() function is a function query that can be used to sort, boost
>>> and as calculated fields. I haven't seen them used in filtering.
>>>
>>> Also, the query() function does *not* do a query, it just says "what
>>> would this document score for this query?"
>>>
>>> Can you describe in English what you are trying to do?
>>>
>>> Upayavira
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
>>>
>>>
>>>
>>> --
>>> Bill Bell
>>> billnb...@gmail.com
>>> cell 720-256-8076
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 7
Re: Issue with if() statement
Forgot last bit:
fq={!switch case.gt.0=$state1
default=$state
func=len($state1)}
On Fri, Jan 1, 2016 at 2:39 PM, William Bell wrote:
> Maybe we can add function value on a switch?
>
> fq={!switch case.gt.0
> default=$state
> func=len($state1)}
>
>
>
> We could add: gt, lt, eq, ge, le ?
>
> gt: greater than
> lt: less than
> eq: equal
> ge: greater than or equal
> le: less than or equal
>
> ??
>
>
>
> On Fri, Jan 1, 2016 at 2:25 PM, William Bell wrote:
>
>> This all started with me trying to use {!switch} to indicate with CO or
>> NY to use. if we pass state1, that is supposed to take precedence, but if
>> nothing is returned, then use state Make sense now?
>>
>> I could not find a way to check for strlen($state1). Which is what I want
>> in the case statement. This just does not work...
>> Something like the following is what I am trying to do:
>>
>>
>> fq={!switch case."anything"=$state1
>> default=$state
>> v=$state1}
>>
>> So I tried the following to set all 50 states:
>>
>>
>> fq={!switch case.all='*:*'
>> case.CO='state:CO'
>> case.NY='state:NY'
>> v=$state1}
>>
>>
>> Obviously Oregon (OR!) is an issue, and it won't work at all plus
>>
>>
>>
>> On Fri, Jan 1, 2016 at 2:15 PM, William Bell wrote:
>>
>>> Another weirdness:
>>>
>>>
>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
>>>
>>>
>>> That does not return anything.
>>>
>>> But if I set v=$state1 I get results.
>>>
>>> Can I not set equivalent variables?
>>>
>>>
>>>
>>> On Fri, Jan 1, 2016 at 2:07 PM, William Bell
>>> wrote:
>>>
Example.
http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
This return 236,000
http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
This returns 10,000
I want to put an IF statement around which v to use.
On Fri, Jan 1, 2016 at 1:52 PM, William Bell
wrote:
> Sure.
>
> If the state:NY returns results filter by state:NY, if it does not,
> then use state:CO. If we have results in NY, use it, otherwise use CO.
>
> OK?
>
> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
>
>>
>>
>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>> > We are getting weird results with if(exists(a),b,c). We are getting
>> b+c!!
>> >
>> >
>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>>
>> >
>> > I am getting NY and CO!
>> >
>> > I only want $state1, which is NY.
>> >
>> > Any other ways to craft this?
>>
>> Does this work at all?
>>
>> The if() function is a function query that can be used to sort, boost
>> and as calculated fields. I haven't seen them used in filtering.
>>
>> Also, the query() function does *not* do a query, it just says "what
>> would this document score for this query?"
>>
>> Can you describe in English what you are trying to do?
>>
>> Upayavira
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
>>>
>>>
>>>
>>> --
>>> Bill Bell
>>> billnb...@gmail.com
>>> cell 720-256-8076
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
Re: Issue with if() statement
Maybe we can add function value on a switch?
fq={!switch case.gt.0
default=$state
func=len($state1)}
We could add: gt, lt, eq, ge, le ?
gt: greater than
lt: less than
eq: equal
ge: greater than or equal
le: less than or equal
??
On Fri, Jan 1, 2016 at 2:25 PM, William Bell wrote:
> This all started with me trying to use {!switch} to indicate with CO or NY
> to use. if we pass state1, that is supposed to take precedence, but if
> nothing is returned, then use state Make sense now?
>
> I could not find a way to check for strlen($state1). Which is what I want
> in the case statement. This just does not work...
> Something like the following is what I am trying to do:
>
>
> fq={!switch case."anything"=$state1
> default=$state
> v=$state1}
>
> So I tried the following to set all 50 states:
>
>
> fq={!switch case.all='*:*'
> case.CO='state:CO'
> case.NY='state:NY'
> v=$state1}
>
>
> Obviously Oregon (OR!) is an issue, and it won't work at all plus
>
>
>
> On Fri, Jan 1, 2016 at 2:15 PM, William Bell wrote:
>
>> Another weirdness:
>>
>>
>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
>>
>>
>> That does not return anything.
>>
>> But if I set v=$state1 I get results.
>>
>> Can I not set equivalent variables?
>>
>>
>>
>> On Fri, Jan 1, 2016 at 2:07 PM, William Bell wrote:
>>
>>> Example.
>>>
>>>
>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>>>
>>>
>>> This return 236,000
>>>
>>>
>>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>>>
>>>
>>> This returns 10,000
>>>
>>> I want to put an IF statement around which v to use.
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 1, 2016 at 1:52 PM, William Bell
>>> wrote:
>>>
Sure.
If the state:NY returns results filter by state:NY, if it does not,
then use state:CO. If we have results in NY, use it, otherwise use CO.
OK?
On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
>
>
> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> > We are getting weird results with if(exists(a),b,c). We are getting
> b+c!!
> >
> >
> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>
> >
> > I am getting NY and CO!
> >
> > I only want $state1, which is NY.
> >
> > Any other ways to craft this?
>
> Does this work at all?
>
> The if() function is a function query that can be used to sort, boost
> and as calculated fields. I haven't seen them used in filtering.
>
> Also, the query() function does *not* do a query, it just says "what
> would this document score for this query?"
>
> Can you describe in English what you are trying to do?
>
> Upayavira
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
>>>
>>>
>>>
>>> --
>>> Bill Bell
>>> billnb...@gmail.com
>>> cell 720-256-8076
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
Re: Issue with if() statement
This all started with me trying to use {!switch} to indicate with CO or NY
to use. if we pass state1, that is supposed to take precedence, but if
nothing is returned, then use state Make sense now?
I could not find a way to check for strlen($state1). Which is what I want
in the case statement. This just does not work...
Something like the following is what I am trying to do:
fq={!switch case."anything"=$state1
default=$state
v=$state1}
So I tried the following to set all 50 states:
fq={!switch case.all='*:*'
case.CO='state:CO'
case.NY='state:NY'
v=$state1}
Obviously Oregon (OR!) is an issue, and it won't work at all plus
On Fri, Jan 1, 2016 at 2:15 PM, William Bell wrote:
> Another weirdness:
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
>
>
> That does not return anything.
>
> But if I set v=$state1 I get results.
>
> Can I not set equivalent variables?
>
>
>
> On Fri, Jan 1, 2016 at 2:07 PM, William Bell wrote:
>
>> Example.
>>
>>
>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>>
>>
>> This return 236,000
>>
>>
>> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>>
>>
>> This returns 10,000
>>
>> I want to put an IF statement around which v to use.
>>
>>
>>
>>
>>
>>
>> On Fri, Jan 1, 2016 at 1:52 PM, William Bell wrote:
>>
>>> Sure.
>>>
>>> If the state:NY returns results filter by state:NY, if it does not, then
>>> use state:CO. If we have results in NY, use it, otherwise use CO.
>>>
>>> OK?
>>>
>>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
>>>
On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> We are getting weird results with if(exists(a),b,c). We are getting
b+c!!
>
>
http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>
> I am getting NY and CO!
>
> I only want $state1, which is NY.
>
> Any other ways to craft this?
Does this work at all?
The if() function is a function query that can be used to sort, boost
and as calculated fields. I haven't seen them used in filtering.
Also, the query() function does *not* do a query, it just says "what
would this document score for this query?"
Can you describe in English what you are trying to do?
Upayavira
>>>
>>>
>>>
>>> --
>>> Bill Bell
>>> billnb...@gmail.com
>>> cell 720-256-8076
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
Re: Issue with if() statement
I'm afraid I cannot see how this can be done - at least without coding.
Basically, when your filter is being evaluated, you want to make use of
knowledge of the main query - for normal queries, that isn't possible,
as they are created independently.
You could use potentially use a "post filter" in which the final set of
documents are passed through a filter - but even then, you wouldn't know
how *why* a document matched, only that it did. So really, you're gonna
need to do this as two queries - one to find out the number of docs
matching your state, and then send a second query based upon that.
With some coding, you could probably get that to be a single request to
Solr, but it is going to remain two queries against the index.
Upayavira
On Fri, Jan 1, 2016, at 09:07 PM, William Bell wrote:
> Example.
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>
> This return 236,000
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>
> This returns 10,000
>
> I want to put an IF statement around which v to use.
>
>
>
>
>
>
> On Fri, Jan 1, 2016 at 1:52 PM, William Bell wrote:
>
> > Sure.
> >
> > If the state:NY returns results filter by state:NY, if it does not, then
> > use state:CO. If we have results in NY, use it, otherwise use CO.
> >
> > OK?
> >
> > On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
> >
> >>
> >>
> >> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> >> > We are getting weird results with if(exists(a),b,c). We are getting
> >> b+c!!
> >> >
> >> >
> >> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
> >>
> >> >
> >> > I am getting NY and CO!
> >> >
> >> > I only want $state1, which is NY.
> >> >
> >> > Any other ways to craft this?
> >>
> >> Does this work at all?
> >>
> >> The if() function is a function query that can be used to sort, boost
> >> and as calculated fields. I haven't seen them used in filtering.
> >>
> >> Also, the query() function does *not* do a query, it just says "what
> >> would this document score for this query?"
> >>
> >> Can you describe in English what you are trying to do?
> >>
> >> Upayavira
> >>
> >
> >
> >
> > --
> > Bill Bell
> > billnb...@gmail.com
> > cell 720-256-8076
> >
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
Re: Issue with if() statement
Another weirdness:
http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
That does not return anything.
But if I set v=$state1 I get results.
Can I not set equivalent variables?
On Fri, Jan 1, 2016 at 2:07 PM, William Bell wrote:
> Example.
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
>
>
> This return 236,000
>
>
> http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
>
>
> This returns 10,000
>
> I want to put an IF statement around which v to use.
>
>
>
>
>
>
> On Fri, Jan 1, 2016 at 1:52 PM, William Bell wrote:
>
>> Sure.
>>
>> If the state:NY returns results filter by state:NY, if it does not, then
>> use state:CO. If we have results in NY, use it, otherwise use CO.
>>
>> OK?
>>
>> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
>>
>>>
>>>
>>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>>> > We are getting weird results with if(exists(a),b,c). We are getting
>>> b+c!!
>>> >
>>> >
>>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>>>
>>> >
>>> > I am getting NY and CO!
>>> >
>>> > I only want $state1, which is NY.
>>> >
>>> > Any other ways to craft this?
>>>
>>> Does this work at all?
>>>
>>> The if() function is a function query that can be used to sort, boost
>>> and as calculated fields. I haven't seen them used in filtering.
>>>
>>> Also, the query() function does *not* do a query, it just says "what
>>> would this document score for this query?"
>>>
>>> Can you describe in English what you are trying to do?
>>>
>>> Upayavira
>>>
>>
>>
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
Re: Issue with if() statement
Example.
http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
This return 236,000
http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state}
This returns 10,000
I want to put an IF statement around which v to use.
On Fri, Jan 1, 2016 at 1:52 PM, William Bell wrote:
> Sure.
>
> If the state:NY returns results filter by state:NY, if it does not, then
> use state:CO. If we have results in NY, use it, otherwise use CO.
>
> OK?
>
> On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
>
>>
>>
>> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
>> > We are getting weird results with if(exists(a),b,c). We are getting
>> b+c!!
>> >
>> >
>> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>>
>> >
>> > I am getting NY and CO!
>> >
>> > I only want $state1, which is NY.
>> >
>> > Any other ways to craft this?
>>
>> Does this work at all?
>>
>> The if() function is a function query that can be used to sort, boost
>> and as calculated fields. I haven't seen them used in filtering.
>>
>> Also, the query() function does *not* do a query, it just says "what
>> would this document score for this query?"
>>
>> Can you describe in English what you are trying to do?
>>
>> Upayavira
>>
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
Re: Issue with if() statement
Sure.
If the state:NY returns results filter by state:NY, if it does not, then
use state:CO. If we have results in NY, use it, otherwise use CO.
OK?
On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
>
>
> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> > We are getting weird results with if(exists(a),b,c). We are getting b+c!!
> >
> >
> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
> >
> > I am getting NY and CO!
> >
> > I only want $state1, which is NY.
> >
> > Any other ways to craft this?
>
> Does this work at all?
>
> The if() function is a function query that can be used to sort, boost
> and as calculated fields. I haven't seen them used in filtering.
>
> Also, the query() function does *not* do a query, it just says "what
> would this document score for this query?"
>
> Can you describe in English what you are trying to do?
>
> Upayavira
>
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
Re: Issue with if() statement
On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> We are getting weird results with if(exists(a),b,c). We are getting b+c!!
>
> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lucene%20v=$state})
>
> I am getting NY and CO!
>
> I only want $state1, which is NY.
>
> Any other ways to craft this?
Does this work at all?
The if() function is a function query that can be used to sort, boost
and as calculated fields. I haven't seen them used in filtering.
Also, the query() function does *not* do a query, it just says "what
would this document score for this query?"
Can you describe in English what you are trying to do?
Upayavira
Re: JVM error v ~StubRoutines::jbyte_disjoint_arraycopy
Thanks.. I upgraded java to latest 1.7 version. Removed all docs from index by deleting directory & re-indexed it again. Solr is not crashing anymore. -- View this message in context: http://lucene.472066.n3.nabble.com/JVM-error-v-StubRoutines-jbyte-disjoint-arraycopy-tp4244603p4248152.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr 6 - Relational Index querying
On Mon, Dec 28, 2015 at 9:11 AM, Joel Bernstein wrote: > In > order to join result sets you would typically need to be working with the > entire result sets from both sides of the join, which may be too slow > without the /export handler. We now have https://issues.apache.org/jira/browse/SOLR-8220 "Read field from docValues for non stored fields" And there is an issue open for how to optimize for cases when fields have both docValues and are stored. Then the other missing optimization is to use a more efficient sort (and possibly defer sorting until streaming) when dealing with an entire result set. -Yonik
using doc values for ICUCollationField
Hi in the reference guide about language analysis you can find an example where docvalues are used in combination with the solr.ICUCollationField type ... ... But the documentation about docvalues itself https://cwiki.apache.org/confluence/display/solr/DocValues says you can only use the docvalue strategy for a limited set of types DocValues are only available for specific field types. The types chosen determine the underlying Lucene docValue type that will be used. The available Solr field types are: - StrField and UUIDField. - If the field is single-valued (i.e., multi-valued is false), Lucene will use the SORTED type. - If the field is multi-valued, Lucene will use the SORTED_SET type. - Any Trie* numeric fields and EnumField. - If the field is single-valued (i.e., multi-valued is false), Lucene will use the NUMERIC type. - If the field is multi-valued, Lucene will use the SORTED_SET type. ICUCollationField isn't mentioned. Any clarification about this? Thanks a lot, Günter
Re: Using post.jr for indexing in Solr 5.4.0
Yes, I'm trying to clean up the text before indexing, but I have not tried on UpdateRequestProcessor. I have been modifying the SolrContentHandler to do that. Regards, Edwin On 1 January 2016 at 16:32, Alexandre Rafalovitch wrote: > Wait? You are trying to clean up text just before indexing? Have you tried > an UpdateRequestProcessor to do that? > > Regards, > Alex > On 1 Jan 2016 1:14 am, "Zheng Lin Edwin Yeo" wrote: > > > Yes, I tried using the latest post.jar, and I got the same error. > > > > I have shortlisted the problem down to the > > org.apache.solr.handler.extraction.ExtractingDocumentLoader, as I have > > modified my SolrContentHandler to remove things like \n, \t and \r from > > being indexed. for this, I have repackaged all the class under > > org.apache.solr.handler.extraction, which lncludes the > > ExtractingDocumentLoader into a new custom jar. > > > > I will work fine if I do not use my modified SolrContentHandler, but that > > means all the \n, \t and \r will be indexed. > > > > Is there any changes with the ExtractingDocumentLoader or other class > under > > org.apache.solr.handler.extraction? > > > > Regards, > > Edwin > > > > > > On 31 December 2015 at 18:09, Erik Hatcher > wrote: > > > > > Looks like you don't have Solr "Cell" lib's pointed to properly in your > > > solrconfig. Try /update/extract directly taking post.jar out if the > > > equation to troubleshoot. > > > > > > What's your exact command line? > > > > > > Erik > > > > > > > On Dec 31, 2015, at 00:42, Zheng Lin Edwin Yeo > > > > wrote: > > > > > > > > Hi, > > > > > > > > Would like to find out, is there any changes to the post.jar for Solr > > > 5.4? > > > > I tried to use the post.jar from Solr 5.3.0, and it gives me the > > > following > > > > error during indexing: > > > > > > > > java.lang.NoSuchMethodError: > > > > org.apache.solr.h > > > > > > > > > > andler.extraction.ExtractingDocumentLoader.(Lorg/apache/solr/request > > > > > > > > > > /SolrQueryRequest;Lorg/apache/solr/update/processor/UpdateRequestProcessor;Lorg/ > > > > > > > > > > apache/tika/config/TikaConfig;Lorg/apache/solr/handler/extraction/ParseContextCo > > > > > > > > > > nfig;Lorg/apache/solr/handler/extraction/SolrContentHandlerFactory;)V > > > name="trace">java.lang.RuntimeException: java.lang.NoSuchMethodError: > > > > org.apache > > > > > > > > > > .solr.handler.extraction.ExtractingDocumentLoader. (Lorg/apache/solr/ > > > > > > > > > > request/SolrQueryRequest;Lorg/apache/solr/update/processor/UpdateRequestProcesso > > > > > > > > > > r;Lorg/apache/tika/config/TikaConfig;Lorg/apache/solr/handler/extraction/ParseCo > > > > > > > > > > ntextConfig;Lorg/apache/solr/handler/extraction/SolrContentHandlerFactory;)V > > > >at > > > > org.apache.solr.servlet.HttpSolrCall.sendError(HttpSolrCall.java:611) > > > > > > > >at > > > org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:472) > > > >at > > > > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilte > > > > r.java:222) > > > >at > > > > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilte > > > > r.java:181) > > > >at > > > > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet > > > > Handler.java:1652) > > > >at > > > > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java > > > > :585) > > > >at > > > > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j > > > > ava:143) > > > >at > > > > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.jav > > > > a:577) > > > >at > > > > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandl > > > > er.java:223) > > > >at > > > > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandl > > > > er.java:1127) > > > >at > > > > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java: > > > > 515) > > > >at > > > > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandle > > > > r.java:185) > > > >at > > > > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandle > > > > r.java:1061) > > > >at > > > > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j > > > > ava:141) > > > >at > > > > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(Cont > > > > extHandlerCollection.java:215) > > > >at > > > > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerColl > > > > ection.java:110) > > > >at > > > > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper > > > > .java:97) > > > >at org.eclipse.jetty.server.Server.handle(Server.java:499) > > > >at > > > org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) > > > >at > > > > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.jav > > > > a:257) > > > >at > > > > org.ecli
Re: Add support in FacetsComponent for facet.method=uif
Is there any interest in this? While i think it's important and inline with faceting available in the new json facet api, I've seen no discussion on it so I'm wondering if it's best I add support for this using a custom facet component even though the majority of the component will be a copy which is prefer to not need to maintain separately. Jamie On Dec 22, 2015 12:37 PM, "Jamie Johnson" wrote: > I had previously piggybacked on another post, but I think it may have been > lost there. I had a need to do UnInvertedField based faceting in the > FacetsComponent and as such started looking at what would be required to > implement something similar to what the JSON Facets based API does in this > regard. The patch that I have in this regard works and is attached to > https://issues.apache.org/jira/browse/SOLR-8096, is that appropriate or > should I create a new ticket to specifically add this support? > > -Jamie >
Re: Using post.jr for indexing in Solr 5.4.0
Wait? You are trying to clean up text just before indexing? Have you tried an UpdateRequestProcessor to do that? Regards, Alex On 1 Jan 2016 1:14 am, "Zheng Lin Edwin Yeo" wrote: > Yes, I tried using the latest post.jar, and I got the same error. > > I have shortlisted the problem down to the > org.apache.solr.handler.extraction.ExtractingDocumentLoader, as I have > modified my SolrContentHandler to remove things like \n, \t and \r from > being indexed. for this, I have repackaged all the class under > org.apache.solr.handler.extraction, which lncludes the > ExtractingDocumentLoader into a new custom jar. > > I will work fine if I do not use my modified SolrContentHandler, but that > means all the \n, \t and \r will be indexed. > > Is there any changes with the ExtractingDocumentLoader or other class under > org.apache.solr.handler.extraction? > > Regards, > Edwin > > > On 31 December 2015 at 18:09, Erik Hatcher wrote: > > > Looks like you don't have Solr "Cell" lib's pointed to properly in your > > solrconfig. Try /update/extract directly taking post.jar out if the > > equation to troubleshoot. > > > > What's your exact command line? > > > > Erik > > > > > On Dec 31, 2015, at 00:42, Zheng Lin Edwin Yeo > > wrote: > > > > > > Hi, > > > > > > Would like to find out, is there any changes to the post.jar for Solr > > 5.4? > > > I tried to use the post.jar from Solr 5.3.0, and it gives me the > > following > > > error during indexing: > > > > > > java.lang.NoSuchMethodError: > > > org.apache.solr.h > > > > > > andler.extraction.ExtractingDocumentLoader.(Lorg/apache/solr/request > > > > > > /SolrQueryRequest;Lorg/apache/solr/update/processor/UpdateRequestProcessor;Lorg/ > > > > > > apache/tika/config/TikaConfig;Lorg/apache/solr/handler/extraction/ParseContextCo > > > > > > nfig;Lorg/apache/solr/handler/extraction/SolrContentHandlerFactory;)V > > name="trace">java.lang.RuntimeException: java.lang.NoSuchMethodError: > > > org.apache > > > > > > .solr.handler.extraction.ExtractingDocumentLoader. (Lorg/apache/solr/ > > > > > > request/SolrQueryRequest;Lorg/apache/solr/update/processor/UpdateRequestProcesso > > > > > > r;Lorg/apache/tika/config/TikaConfig;Lorg/apache/solr/handler/extraction/ParseCo > > > > > > ntextConfig;Lorg/apache/solr/handler/extraction/SolrContentHandlerFactory;)V > > >at > > > org.apache.solr.servlet.HttpSolrCall.sendError(HttpSolrCall.java:611) > > > > > >at > > org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:472) > > >at > > > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilte > > > r.java:222) > > >at > > > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilte > > > r.java:181) > > >at > > > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet > > > Handler.java:1652) > > >at > > > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java > > > :585) > > >at > > > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j > > > ava:143) > > >at > > > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.jav > > > a:577) > > >at > > > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandl > > > er.java:223) > > >at > > > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandl > > > er.java:1127) > > >at > > > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java: > > > 515) > > >at > > > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandle > > > r.java:185) > > >at > > > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandle > > > r.java:1061) > > >at > > > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j > > > ava:141) > > >at > > > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(Cont > > > extHandlerCollection.java:215) > > >at > > > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerColl > > > ection.java:110) > > >at > > > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper > > > .java:97) > > >at org.eclipse.jetty.server.Server.handle(Server.java:499) > > >at > > org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) > > >at > > > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.jav > > > a:257) > > >at > > > org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java > > > :540) > > >at > > > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPoo > > > l.java:635) > > >at > > > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool > > > .java:555) > > >at java.lang.Thread.run(Thread.java:745) > > > Caused by: java.lang.NoSuchMethodError: > > > org.apache.solr.handler.extraction.Extra > > > > > > ctingDocumentLoader. (Lorg/apache/solr/request/SolrQueryRequest;
