date:20151112

Re: Search query speed

2015-11-12 Thread Emir Arnautovic

What are HW specs. 4 threads is not much but still makes test less 
deterministic, especially in case when queries are not equally "heavy".


Can you also collect QTime from Solr response and see if differences are 
caused by networking.


Emir

On 11.11.2015 20:44, John Stric wrote:

There is a .NET app that is calling solr. I am measuring time span using
.NET provided methods. It used to take about 42 msec and it started taking
66 msec from the time to compose the call and query solr, get results and
parse them back. Interestingly today it was close to 44 msec.
I am testing using 4 threads and 1000 iterations i.e. each thread makes 250
requests. I then do the average.

The query is being done using dismax parser with mm, qf, qs and bf. There
are 5 query fields. The query includes filter on 3 fields and facet on two
fields

No changes were done: no new docs, no updated or deleted docs. I did try to
restart machine and test multiple time/multiple ways and still the average
was about 66 msec.



On Wed, Nov 11, 2015 at 12:18 PM, Chris Hostetter 
wrote:


: The speed of particular query has gone from about 42 msec to 66 msec
: without any changes.

1) Define "speed" ?

how are you measuring?
where are you measuring?
are you measuring averages? over what sample size?

2) define "particular query" ?

what types of queries?
what types of params are in the request?
what do the results look like?

3) Define "any changes" ?

new docs?
deleted docs?
updated docs?
restarted server?
restarted solr?
increased query load?



-Hoss
http://www.lucidworks.com/



--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/

Re: fl=value equals?

2015-11-12 Thread billnbell

fl=$b tells me it works. Or I can do a sort=$b asc

The idea is to calculate a score but only include geo if it is not a national 
search. Do we want to send in a parameter into the QT which allows us to omit 
geo from national searches


Bill Bell
Sent from mobile

> On Nov 11, 2015, at 1:15 AM, Upayavira  wrote:
> 
> I concur with Jan - what does b= do? 
> 
> Also asking, how did you identify that it worked?
> 
> Upayavira
> 
>> On Wed, Nov 11, 2015, at 02:58 AM, William Bell wrote:
>> I was able to get it to work kinda with a map().
>> 
>> http://localhost:8983/solr/select?q=*:*=1=
>> 
>> map($radius,1,1,0,geodist())
>> 
>> Where 1= National
>> 
>> Do you have an example of a SearchComponent? It would be pretty easy to
>> copy map() and develop an equals() right?
>> 
>> if(equals($radius, 'national'), 0, geodist())
>> 
>> This would probably be useful for everyone.
>> 
>> On Tue, Nov 10, 2015 at 4:05 PM, Jan Høydahl 
>> wrote:
>> 
>>> Where is your “b” parameter used? I think that instead of trying to set a
>>> new “b” http param (which solr will not evaluate as a function), you should
>>> instead try to insert your function or switch qParser directly where the
>>> “b” param is used, e.g. in a bq or similar.
>>> 
>>> A bit heavy weight, but you could of course write a custom SearchComponent
>>> to construct your “b” parameter...
>>> 
>>> --
>>> Jan Høydahl, search solution architect
>>> Cominvent AS - www.cominvent.com
>>> 
 10. nov. 2015 kl. 23.52 skrev William Bell :
 
 We are trying to look at a value, and change another value based on that.
 
 For example, for national search we want to pass in radius=national, and
 then set another variable equal to 0, else set the other variable = to
 geodist() calculation.
 
 We tried {!switch} but this only appears to work on fq/q. There is no
 function for constants for equals
>>> http://localhost:8983/solr/select?q=*:*=national=if(equals($radius,'national'),0,geodist())
 
 This does not work:
 
 http://localhost:8983/solr/select?q=*:*=national={!switch
 case.national=0 default=geodist() v=$radius}
 
 Ideas?
 
 
 
 --
 Bill Bell
 billnb...@gmail.com
 cell 720-256-8076
>> 
>> 
>> -- 
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076

Re: fl=value equals?

2015-11-12 Thread Upayavira

Okay, makes sense. As to your question - making a new ValueSourceParser
that handles 'equals' sounds pretty straight-forward.

If it helps, I have somewhere an Ant project that will unpack Solr and
compile custom components against it. I could push that to github or
something.

Upayavira

On Thu, Nov 12, 2015, at 07:59 AM, billnb...@gmail.com wrote:
> fl=$b tells me it works. Or I can do a sort=$b asc
> 
> The idea is to calculate a score but only include geo if it is not a
> national search. Do we want to send in a parameter into the QT which
> allows us to omit geo from national searches
> 
> 
> Bill Bell
> Sent from mobile
> 
> > On Nov 11, 2015, at 1:15 AM, Upayavira  wrote:
> > 
> > I concur with Jan - what does b= do? 
> > 
> > Also asking, how did you identify that it worked?
> > 
> > Upayavira
> > 
> >> On Wed, Nov 11, 2015, at 02:58 AM, William Bell wrote:
> >> I was able to get it to work kinda with a map().
> >> 
> >> http://localhost:8983/solr/select?q=*:*=1=
> >> 
> >> map($radius,1,1,0,geodist())
> >> 
> >> Where 1= National
> >> 
> >> Do you have an example of a SearchComponent? It would be pretty easy to
> >> copy map() and develop an equals() right?
> >> 
> >> if(equals($radius, 'national'), 0, geodist())
> >> 
> >> This would probably be useful for everyone.
> >> 
> >> On Tue, Nov 10, 2015 at 4:05 PM, Jan Høydahl 
> >> wrote:
> >> 
> >>> Where is your “b” parameter used? I think that instead of trying to set a
> >>> new “b” http param (which solr will not evaluate as a function), you 
> >>> should
> >>> instead try to insert your function or switch qParser directly where the
> >>> “b” param is used, e.g. in a bq or similar.
> >>> 
> >>> A bit heavy weight, but you could of course write a custom SearchComponent
> >>> to construct your “b” parameter...
> >>> 
> >>> --
> >>> Jan Høydahl, search solution architect
> >>> Cominvent AS - www.cominvent.com
> >>> 
>  10. nov. 2015 kl. 23.52 skrev William Bell :
>  
>  We are trying to look at a value, and change another value based on that.
>  
>  For example, for national search we want to pass in radius=national, and
>  then set another variable equal to 0, else set the other variable = to
>  geodist() calculation.
>  
>  We tried {!switch} but this only appears to work on fq/q. There is no
>  function for constants for equals
> >>> http://localhost:8983/solr/select?q=*:*=national=if(equals($radius,'national'),0,geodist())
>  
>  This does not work:
>  
>  http://localhost:8983/solr/select?q=*:*=national={!switch
>  case.national=0 default=geodist() v=$radius}
>  
>  Ideas?
>  
>  
>  
>  --
>  Bill Bell
>  billnb...@gmail.com
>  cell 720-256-8076
> >> 
> >> 
> >> -- 
> >> Bill Bell
> >> billnb...@gmail.com
> >> cell 720-256-8076

Re: Parent/Child (Nested Document) Faceting

2015-11-12 Thread Alessandro Benedetti

Last addition, in the case of multi-level hierarchy.
I think I found what we can not reproduce :

*json.facet*={
top_reviewers: {
type: terms,
field: author_s,
facet: {
reviewCount: "unique(parent_s)",
facet: {
type: terms,
field: id,
domain: {
blockParent: "type_s:book"
},
   facet: {
   bookCount: "unique(id)"}
}
}
}
}

Example Response :

facets":{
"count":7,
"top_reviewers":{
  "buckets":[{
  "val":"commenterYonik",
  "count":4,
  "reviewCount":2,
  "facet":{
"buckets":[{
"val":"book1",
"count":1,
*"bookCount":1},*
  {
"val":"book2",
"count":1,
*"bookCount":1}]}},*
{
  "val":"commenterAlex",
  "count":3,
  "reviewCount":2,
  "facet":{
"buckets":[{
"val":"book2",
"count":1,
   * "bookCount":1*}]}}]}}}


Ideally I want to be able to move bookCount stat at the level of
reviewCount ( using a sort of path in the ancestors) .
Something like :

json.facet={
top_reviewers: {
type: terms,
field: author_s,
facet: {
reviewCount: "unique(parent_s)",
stat: {
domain: {
blockParent: "type_s:review"
},
bookCount: "unique(parent_s)"
}
}
}
}

The 3 level edge case could be solved using a parent_s field and the _root_
field.

But in a N level scenario we would need a way to specify a path and be able
to provide this kind of analytics.

Sorry for the spam.


Cheers

On 12 November 2015 at 11:15, Alessandro Benedetti 
wrote:

> I was experimenting with multi-level hierarchy of nested objects.
>
> the _root_ field will always point to  the root parent id.
> If I model Books - Reviews - Comments , where do I have the reference to
> the parent ?
> I think we are getting closer to the understanding of the ES functionality.
>
> It should allow to search in Level N ( comments for example) and then
> facet over the unique values of :
> 1) parent - Given my comments to reviews of books, count all the different
> reviews I commented* ( wondering how to access the parent of a child)*
> 2) grand parent - Given my comments to reviews of books, count all the
> different books, I commented a review of ( tried this and it is working)
> 3) Any ancestor though the path
>
> Cheers
>
> On 12 November 2015 at 10:25, Alessandro Benedetti 
> wrote:
>
>> Hi Mikhail,
>> how about this :
>>
>> json.facet={
>> top_reviewers: {
>> type: terms,
>> field: author_s,
>> sort: "booksCount desc",
>> facet: {
>> booksCount: "unique(_root_)"
>> }
>> }
>> }
>>
>> We query on children ( comments) and we calculate that facets.
>> This should satisfy your test requirement:
>>
>>
>> http://localhost:8983/solr/demo/select?q=*:*=json=true=id,comment_t={top_reviewers:
>> {type: terms,field: author_s,sort: "booksCount desc",facet: {booksCount:
>> "unique(_root_)"}}}
>>
>> Example Response :
>>
>> "top_reviewers":{
>>   "buckets":[{
>>   "val":"dan",
>>   "count":2,
>>   "booksCount":2},
>> {
>>   "val":"yonik",
>>   "count":2,
>>   "booksCount":2},
>> {
>>   "val":"Brandon Sanderson",
>>   "count":1,
>>   "booksCount":1},
>> *{
>>   "val":"Mary",
>>   "count":2,
>>   "booksCount":1}*
>>
>> ...
>>
>> Wondering which kind of scenarios can rise if we consider a multi-level
>> hierarchy...
>>
>> Cheers
>>
>> On 11 November 2015 at 22:26, Mikhail Khludnev <
>> mkhlud...@griddynamics.com> wrote:
>>
>>> I found that example has not enough data to reproduce this functionality.
>>> what if Mary left the same comment to the same book (book2_c4), then we
>>> search for th* across comments
>>>
>>>
>>> http://localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=csv=true=author_s,comment_t,id
>>>
>>> and get
>>>
>>> author_s,comment_t,id
>>> dan,This book was too long.,book1_c2
>>> yonik,Ahead of its time... I wonder if it helped inspire The
>>> Matrix?,book2_c1
>>> dan,A pizza boy for the Mafia franchise? Really?,book2_c2
>>> mary,Neal is so creative and detailed! Loved the metaverse!,book2_c3
>>> mary,Neal is so creative and detailed! Loved the metaverse!,book2_c4
>>>
>>> then, I wish to calculate author facet, but count them in books
>>> (rollup to parents)!
>>>
>>> dan(2) - commented both books
>>> yonik(1) - only second one
>>> *mary(1)*  - only second one, despite twice
>>>
>>> So, far I'm ablle only
>>>
>>>
>>>

Re: Parent/Child (Nested Document) Faceting

2015-11-12 Thread Mikhail Khludnev

Alessandro,

> facet: {booksCount:"unique(_root_)"}
is a pretty cool finding. it's what literally Elastic does in
"reverse-nested-aggregation". it's interesting how much it costs for
shards. I'll look deeper.
Thanks, Alessandro!
Yonik, JSON Facets rocks!

On Thu, Nov 12, 2015 at 1:25 PM, Alessandro Benedetti  wrote:

> Hi Mikhail,
> how about this :
>
> json.facet={
> top_reviewers: {
> type: terms,
> field: author_s,
> sort: "booksCount desc",
> facet: {
> booksCount: "unique(_root_)"
> }
> }
> }
>
> We query on children ( comments) and we calculate that facets.
> This should satisfy your test requirement:
>
>
> http://localhost:8983/solr/demo/select?q=*:*=json=true=id,comment_t={top_reviewers
> :
> {type: terms,field: author_s,sort: "booksCount desc",facet: {booksCount:
> "unique(_root_)"}}}
>
> Example Response :
>
> "top_reviewers":{
>   "buckets":[{
>   "val":"dan",
>   "count":2,
>   "booksCount":2},
> {
>   "val":"yonik",
>   "count":2,
>   "booksCount":2},
> {
>   "val":"Brandon Sanderson",
>   "count":1,
>   "booksCount":1},
> *{
>   "val":"Mary",
>   "count":2,
>   "booksCount":1}*
>
> ...
>
> Wondering which kind of scenarios can rise if we consider a multi-level
> hierarchy...
>
> Cheers
>
> On 11 November 2015 at 22:26, Mikhail Khludnev  >
> wrote:
>
> > I found that example has not enough data to reproduce this functionality.
> > what if Mary left the same comment to the same book (book2_c4), then we
> > search for th* across comments
> >
> >
> >
> http://localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=csv=true=author_s,comment_t,id
> >
> > and get
> >
> > author_s,comment_t,id
> > dan,This book was too long.,book1_c2
> > yonik,Ahead of its time... I wonder if it helped inspire The
> > Matrix?,book2_c1
> > dan,A pizza boy for the Mafia franchise? Really?,book2_c2
> > mary,Neal is so creative and detailed! Loved the metaverse!,book2_c3
> > mary,Neal is so creative and detailed! Loved the metaverse!,book2_c4
> >
> > then, I wish to calculate author facet, but count them in books
> > (rollup to parents)!
> >
> > dan(2) - commented both books
> > yonik(1) - only second one
> > *mary(1)*  - only second one, despite twice
> >
> > So, far I'm ablle only
> >
> >
> >
> localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=json=true=author_s,comment_t,id={top_reviewers
> > : { type: terms, field: author_s}}
> >
> > "top_reviewers":{
> >   "buckets":[{
> >   "val":"dan",
> >   "count":2},
> > {
> >   "val":"mary",
> >   "count":2},
> > {
> >   "val":"yonik",
> >   "count":1}]}}}
> >
> > but it's comments mary(2), not books!
> >
> > Neither  domain: { blockParent : "type_s:book" } nor  domain: {
> > blockChildren : "type_s:book" } don't help.
> >
> > I tried to nest a facet with specifying a domain, it's just ignored
> >
> >
> localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=json=true=author_s,comment_t,id={top_reviewers
> > : { type: terms, field: author_s, in_books : { type: terms, field:
> > author_s,  domain: { blockParent : \"type_s:book\" 
> >
> >
> >
> >
> > On Wed, Nov 11, 2015 at 6:31 PM, Yonik Seeley  wrote:
> >
> > > On Mon, Nov 9, 2015 at 2:37 PM, Mikhail Khludnev
> > >  wrote:
> > > > Yonik,
> > > >
> > > > I wonder is there a plan or a vision for something like
> > > >
> > >
> >
> https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-reverse-nested-aggregation.html
> > > > under JSON facets?
> > >
> > > Hmmm, I couldn't quite grok that complicated command syntax... but the
> > > description seems straight-forward enough:
> > >
> > > "The following aggregations will return the top commenters' username
> > > that have commented and per top commenter the top tags of the issues
> > > the user has commented on:"
> > >
> > > So if I translate that into "books" and "reviews" that I use here:
> > > http://yonik.com/solr-nested-objects/
> > >
> > > it sounds like we start with a set of book objects, then map to the
> > > child domain to facet on comments, then map back to the parent domain
> > > to facet on books again.
> > >
> > > From that blog, this is the command that finds top review authors:
> > >
> > > json.facet={
> > >   top_reviewers : {
> > > type: terms,
> > > field: author_s,
> > > domain: { blockChildren : "type_s:book" }
> > >   }
> > > }
> > >
> > > Now we just need to add a sub-facet that switches back to the parent
> > > domain to facet on something there (like genre... equiv to "tags" in
> > > the ES example):
> > >
> > > son.facet={
> > >   top_reviewers : {
> > > type: terms,
> > > field: author_s,
> > > domain: { blockChildren : "type_s:book" },

Re: Parent/Child (Nested Document) Faceting

2015-11-12 Thread Alessandro Benedetti

Hi Mikhail,
how about this :

json.facet={
top_reviewers: {
type: terms,
field: author_s,
sort: "booksCount desc",
facet: {
booksCount: "unique(_root_)"
}
}
}

We query on children ( comments) and we calculate that facets.
This should satisfy your test requirement:

http://localhost:8983/solr/demo/select?q=*:*=json=true=id,comment_t={top_reviewers:
{type: terms,field: author_s,sort: "booksCount desc",facet: {booksCount:
"unique(_root_)"}}}

Example Response :

"top_reviewers":{
  "buckets":[{
  "val":"dan",
  "count":2,
  "booksCount":2},
{
  "val":"yonik",
  "count":2,
  "booksCount":2},
{
  "val":"Brandon Sanderson",
  "count":1,
  "booksCount":1},
*{
  "val":"Mary",
  "count":2,
  "booksCount":1}*

...

Wondering which kind of scenarios can rise if we consider a multi-level
hierarchy...

Cheers

On 11 November 2015 at 22:26, Mikhail Khludnev 
wrote:

> I found that example has not enough data to reproduce this functionality.
> what if Mary left the same comment to the same book (book2_c4), then we
> search for th* across comments
>
>
> http://localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=csv=true=author_s,comment_t,id
>
> and get
>
> author_s,comment_t,id
> dan,This book was too long.,book1_c2
> yonik,Ahead of its time... I wonder if it helped inspire The
> Matrix?,book2_c1
> dan,A pizza boy for the Mafia franchise? Really?,book2_c2
> mary,Neal is so creative and detailed! Loved the metaverse!,book2_c3
> mary,Neal is so creative and detailed! Loved the metaverse!,book2_c4
>
> then, I wish to calculate author facet, but count them in books
> (rollup to parents)!
>
> dan(2) - commented both books
> yonik(1) - only second one
> *mary(1)*  - only second one, despite twice
>
> So, far I'm ablle only
>
>
> localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=json=true=author_s,comment_t,id={top_reviewers
> : { type: terms, field: author_s}}
>
> "top_reviewers":{
>   "buckets":[{
>   "val":"dan",
>   "count":2},
> {
>   "val":"mary",
>   "count":2},
> {
>   "val":"yonik",
>   "count":1}]}}}
>
> but it's comments mary(2), not books!
>
> Neither  domain: { blockParent : "type_s:book" } nor  domain: {
> blockChildren : "type_s:book" } don't help.
>
> I tried to nest a facet with specifying a domain, it's just ignored
>
> localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=json=true=author_s,comment_t,id={top_reviewers
> : { type: terms, field: author_s, in_books : { type: terms, field:
> author_s,  domain: { blockParent : \"type_s:book\" 
>
>
>
>
> On Wed, Nov 11, 2015 at 6:31 PM, Yonik Seeley  wrote:
>
> > On Mon, Nov 9, 2015 at 2:37 PM, Mikhail Khludnev
> >  wrote:
> > > Yonik,
> > >
> > > I wonder is there a plan or a vision for something like
> > >
> >
> https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-reverse-nested-aggregation.html
> > > under JSON facets?
> >
> > Hmmm, I couldn't quite grok that complicated command syntax... but the
> > description seems straight-forward enough:
> >
> > "The following aggregations will return the top commenters' username
> > that have commented and per top commenter the top tags of the issues
> > the user has commented on:"
> >
> > So if I translate that into "books" and "reviews" that I use here:
> > http://yonik.com/solr-nested-objects/
> >
> > it sounds like we start with a set of book objects, then map to the
> > child domain to facet on comments, then map back to the parent domain
> > to facet on books again.
> >
> > From that blog, this is the command that finds top review authors:
> >
> > json.facet={
> >   top_reviewers : {
> > type: terms,
> > field: author_s,
> > domain: { blockChildren : "type_s:book" }
> >   }
> > }
> >
> > Now we just need to add a sub-facet that switches back to the parent
> > domain to facet on something there (like genre... equiv to "tags" in
> > the ES example):
> >
> > son.facet={
> >   top_reviewers : {
> > type: terms,
> > field: author_s,
> > domain: { blockChildren : "type_s:book" },
> >
> > facet : {
> >   type:terms,
> >   field:genre,
> >   domain:{blockParent:"type_s:book"}
> > }
> >
> >   }
> > }
> >
> >
> >
> > While there is certainly more work do be done with joins /
> > block-joins, it seems like we can already do that specific example at
> > least.
> >
> > -Yonik
> >
>
>
>
> --
> Sincerely yours
> Mikhail Khludnev
> Principal Engineer,
> Grid Dynamics
>
> 
> 
>



-- 
--

Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti

"Tyger, tyger burning bright
In the forests of the night,
What

Re: Parent/Child (Nested Document) Faceting

2015-11-12 Thread Alessandro Benedetti

I was experimenting with multi-level hierarchy of nested objects.

the _root_ field will always point to  the root parent id.
If I model Books - Reviews - Comments , where do I have the reference to
the parent ?
I think we are getting closer to the understanding of the ES functionality.

It should allow to search in Level N ( comments for example) and then facet
over the unique values of :
1) parent - Given my comments to reviews of books, count all the different
reviews I commented* ( wondering how to access the parent of a child)*
2) grand parent - Given my comments to reviews of books, count all the
different books, I commented a review of ( tried this and it is working)
3) Any ancestor though the path

Cheers

On 12 November 2015 at 10:25, Alessandro Benedetti 
wrote:

> Hi Mikhail,
> how about this :
>
> json.facet={
> top_reviewers: {
> type: terms,
> field: author_s,
> sort: "booksCount desc",
> facet: {
> booksCount: "unique(_root_)"
> }
> }
> }
>
> We query on children ( comments) and we calculate that facets.
> This should satisfy your test requirement:
>
>
> http://localhost:8983/solr/demo/select?q=*:*=json=true=id,comment_t={top_reviewers:
> {type: terms,field: author_s,sort: "booksCount desc",facet: {booksCount:
> "unique(_root_)"}}}
>
> Example Response :
>
> "top_reviewers":{
>   "buckets":[{
>   "val":"dan",
>   "count":2,
>   "booksCount":2},
> {
>   "val":"yonik",
>   "count":2,
>   "booksCount":2},
> {
>   "val":"Brandon Sanderson",
>   "count":1,
>   "booksCount":1},
> *{
>   "val":"Mary",
>   "count":2,
>   "booksCount":1}*
>
> ...
>
> Wondering which kind of scenarios can rise if we consider a multi-level
> hierarchy...
>
> Cheers
>
> On 11 November 2015 at 22:26, Mikhail Khludnev  > wrote:
>
>> I found that example has not enough data to reproduce this functionality.
>> what if Mary left the same comment to the same book (book2_c4), then we
>> search for th* across comments
>>
>>
>> http://localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=csv=true=author_s,comment_t,id
>>
>> and get
>>
>> author_s,comment_t,id
>> dan,This book was too long.,book1_c2
>> yonik,Ahead of its time... I wonder if it helped inspire The
>> Matrix?,book2_c1
>> dan,A pizza boy for the Mafia franchise? Really?,book2_c2
>> mary,Neal is so creative and detailed! Loved the metaverse!,book2_c3
>> mary,Neal is so creative and detailed! Loved the metaverse!,book2_c4
>>
>> then, I wish to calculate author facet, but count them in books
>> (rollup to parents)!
>>
>> dan(2) - commented both books
>> yonik(1) - only second one
>> *mary(1)*  - only second one, despite twice
>>
>> So, far I'm ablle only
>>
>>
>> localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=json=true=author_s,comment_t,id={top_reviewers
>> : { type: terms, field: author_s}}
>>
>> "top_reviewers":{
>>   "buckets":[{
>>   "val":"dan",
>>   "count":2},
>> {
>>   "val":"mary",
>>   "count":2},
>> {
>>   "val":"yonik",
>>   "count":1}]}}}
>>
>> but it's comments mary(2), not books!
>>
>> Neither  domain: { blockParent : "type_s:book" } nor  domain: {
>> blockChildren : "type_s:book" } don't help.
>>
>> I tried to nest a facet with specifying a domain, it's just ignored
>>
>> localhost:8983/solr/techproducts/select?q=comment_t%3Ath*=json=true=author_s,comment_t,id={top_reviewers
>> : { type: terms, field: author_s, in_books : { type: terms, field:
>> author_s,  domain: { blockParent : \"type_s:book\" 
>>
>>
>>
>>
>> On Wed, Nov 11, 2015 at 6:31 PM, Yonik Seeley  wrote:
>>
>> > On Mon, Nov 9, 2015 at 2:37 PM, Mikhail Khludnev
>> >  wrote:
>> > > Yonik,
>> > >
>> > > I wonder is there a plan or a vision for something like
>> > >
>> >
>> https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-reverse-nested-aggregation.html
>> > > under JSON facets?
>> >
>> > Hmmm, I couldn't quite grok that complicated command syntax... but the
>> > description seems straight-forward enough:
>> >
>> > "The following aggregations will return the top commenters' username
>> > that have commented and per top commenter the top tags of the issues
>> > the user has commented on:"
>> >
>> > So if I translate that into "books" and "reviews" that I use here:
>> > http://yonik.com/solr-nested-objects/
>> >
>> > it sounds like we start with a set of book objects, then map to the
>> > child domain to facet on comments, then map back to the parent domain
>> > to facet on books again.
>> >
>> > From that blog, this is the command that finds top review authors:
>> >
>> > json.facet={
>> >   top_reviewers : {
>> > type: terms,
>> > field: author_s,
>> > domain: { blockChildren :

Json facet api NullPointerException

2015-11-12 Thread Yago Riveiro

Hi,

I'm hitting this NullPointerException using the json facet API.

Same query using Facet component is working.

Json facet query:

curl -s http://node1:8983/solr/metrics/query -d
'q=datetime:[2015-10-01T00:00:00Z TO
2015-10-04T23:59:59Z]=0={
urls: {
type: terms,
field: url,
limit: -1,
sort: index,
numBuckets: true
}}'

Facet component query:

http://node1:8983/solr/metrics/query?q=datetime:[2015-10-01T00:00:00Z%20TO%202015-10-04T23:59:59Z]=true=url=1=-1=0=json=1=index

Total elements returned: 1971203
Total unique elements returned: 307570

Json facet api response:

2015-11-12 15:29:53.130 ERROR (qtp1510067370-34151) [c:metrics:shard1
r:core_node5 x:metrics_shard1_replica2] o.a.s.s.SolrDispatchFilter
null:java.lang.NullPointerException
at
org.apache.solr.search.facet.FacetFieldProcessorFCBase$1.lessThan(FacetField.java:573)
at
org.apache.solr.search.facet.FacetFieldProcessorFCBase$1.lessThan(FacetField.java:570)
at
org.apache.lucene.util.PriorityQueue.upHeap(PriorityQueue.java:258)
at org.apache.lucene.util.PriorityQueue.add(PriorityQueue.java:135)
at
org.apache.solr.search.facet.FacetFieldProcessorFCBase.findTopSlots(FacetField.java:603)
at
org.apache.solr.search.facet.FacetFieldProcessorFCBase.getFieldCacheCounts(FacetField.java:547)
at
org.apache.solr.search.facet.FacetFieldProcessorFCBase.process(FacetField.java:512)
at
org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:222)
at
org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:313)
at
org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:57)
at
org.apache.solr.search.facet.FacetModule.process(FacetModule.java:87)
at
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:277)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:2068)
at
org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:669)
at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:462)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:214)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:179)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.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.java:257)
at
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)



-
Best regards
--
View this message in context: 
http://lucene.472066.n3.nabble.com/Json-facet-api-NullPointerException-tp4239900.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Explicit commit with openSearcher=false

2015-11-12 Thread Mark Miller

You can pass arbitrary params with Solrj. The API usage is just a little
more arcane.

- Mark

On Wed, Nov 11, 2015 at 11:33 PM Sathyakumar Seshachalam <
sathyakumar_seshacha...@trimble.com> wrote:

> I intend to use SolrJ. I only saw the below overloaded commit method in
> documentation (http://lucene.apache.org/solr/4_10_3/solr-solrj/index.html)
> of class ³org.apache.solr.client.solrj.SolrServer"
>
> public UpdateResponse commit(boolean waitFlush, boolean waitSearcher,
> boolean softCommit).
>
>
> And I assumed waitSearcher is not the same as openSearcher.  (From the
> documentation atleast it would seem that waitSearcher when false only does
> not block the call, but a searcher is still opened).
> None of the add methods take a openSearcher param either.
>
> Regards
> Sathya
>
>
> On 11/11/15, 11:58 PM, "Chris Hostetter"  wrote:
>
> >
> >: I saw mention of openSearcher for SolrJ, so I looked in the source of
> >: the UpdateRequestHandler, and there is no mention of openSearcher in
> >: there that I can see, for XML, JSON or SolrJ requests.
> >:
> >: So my take is that this isn't possible right now :-(
> >
> >It's handled by the Loaders - all of which (i think?) delegate to
> >RequestHandlerUtils.handleCommit to generate the CommitUpdateCommand
> >according to the relevant UpdateParams.
> >
> >Most of the constants you see in UpdateRequestHandler look like dead code
> >that should be removed.
> >
> >
> >-Hoss
> >http://www.lucidworks.com/
>
> --
- Mark
about.me/markrmiller

Re: Json facet api NullPointerException

2015-11-12 Thread Yonik Seeley

Thanks for the report Yago,
What version is this?

-Yonik


On Thu, Nov 12, 2015 at 10:53 AM, Yago Riveiro  wrote:
> Hi,
>
> I'm hitting this NullPointerException using the json facet API.
>
> Same query using Facet component is working.
>
> Json facet query:
>
> curl -s http://node1:8983/solr/metrics/query -d
> 'q=datetime:[2015-10-01T00:00:00Z TO
> 2015-10-04T23:59:59Z]=0={
> urls: {
> type: terms,
> field: url,
> limit: -1,
> sort: index,
> numBuckets: true
> }}'
>
> Facet component query:
>
> http://node1:8983/solr/metrics/query?q=datetime:[2015-10-01T00:00:00Z%20TO%202015-10-04T23:59:59Z]=true=url=1=-1=0=json=1=index
>
> Total elements returned: 1971203
> Total unique elements returned: 307570
>
> Json facet api response:
>
> 2015-11-12 15:29:53.130 ERROR (qtp1510067370-34151) [c:metrics:shard1
> r:core_node5 x:metrics_shard1_replica2] o.a.s.s.SolrDispatchFilter
> null:java.lang.NullPointerException
> at
> org.apache.solr.search.facet.FacetFieldProcessorFCBase$1.lessThan(FacetField.java:573)
> at
> org.apache.solr.search.facet.FacetFieldProcessorFCBase$1.lessThan(FacetField.java:570)
> at
> org.apache.lucene.util.PriorityQueue.upHeap(PriorityQueue.java:258)
> at org.apache.lucene.util.PriorityQueue.add(PriorityQueue.java:135)
> at
> org.apache.solr.search.facet.FacetFieldProcessorFCBase.findTopSlots(FacetField.java:603)
> at
> org.apache.solr.search.facet.FacetFieldProcessorFCBase.getFieldCacheCounts(FacetField.java:547)
> at
> org.apache.solr.search.facet.FacetFieldProcessorFCBase.process(FacetField.java:512)
> at
> org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:222)
> at
> org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:313)
> at
> org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:57)
> at
> org.apache.solr.search.facet.FacetModule.process(FacetModule.java:87)
> at
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:277)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2068)
> at
> org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:669)
> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:462)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:214)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:179)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.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.java:257)
> at
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
>
>
>
> -
> Best regards
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/Json-facet-api-NullPointerException-tp4239900.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Re: Json facet api NullPointerException

2015-11-12 Thread Yago Riveiro

Solr 5.3.1


—/Yago Riveiro

On Thu, Nov 12, 2015 at 4:21 PM, Yonik Seeley  wrote:

> Thanks for the report Yago,
> What version is this?
> -Yonik
> On Thu, Nov 12, 2015 at 10:53 AM, Yago Riveiro  wrote:
>> Hi,
>>
>> I'm hitting this NullPointerException using the json facet API.
>>
>> Same query using Facet component is working.
>>
>> Json facet query:
>>
>> curl -s http://node1:8983/solr/metrics/query -d
>> 'q=datetime:[2015-10-01T00:00:00Z TO
>> 2015-10-04T23:59:59Z]=0={
>> urls: {
>> type: terms,
>> field: url,
>> limit: -1,
>> sort: index,
>> numBuckets: true
>> }}'
>>
>> Facet component query:
>>
>> http://node1:8983/solr/metrics/query?q=datetime:[2015-10-01T00:00:00Z%20TO%202015-10-04T23:59:59Z]=true=url=1=-1=0=json=1=index
>>
>> Total elements returned: 1971203
>> Total unique elements returned: 307570
>>
>> Json facet api response:
>>
>> 2015-11-12 15:29:53.130 ERROR (qtp1510067370-34151) [c:metrics:shard1
>> r:core_node5 x:metrics_shard1_replica2] o.a.s.s.SolrDispatchFilter
>> null:java.lang.NullPointerException
>> at
>> org.apache.solr.search.facet.FacetFieldProcessorFCBase$1.lessThan(FacetField.java:573)
>> at
>> org.apache.solr.search.facet.FacetFieldProcessorFCBase$1.lessThan(FacetField.java:570)
>> at
>> org.apache.lucene.util.PriorityQueue.upHeap(PriorityQueue.java:258)
>> at org.apache.lucene.util.PriorityQueue.add(PriorityQueue.java:135)
>> at
>> org.apache.solr.search.facet.FacetFieldProcessorFCBase.findTopSlots(FacetField.java:603)
>> at
>> org.apache.solr.search.facet.FacetFieldProcessorFCBase.getFieldCacheCounts(FacetField.java:547)
>> at
>> org.apache.solr.search.facet.FacetFieldProcessorFCBase.process(FacetField.java:512)
>> at
>> org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:222)
>> at
>> org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:313)
>> at
>> org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:57)
>> at
>> org.apache.solr.search.facet.FacetModule.process(FacetModule.java:87)
>> at
>> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:277)
>> at
>> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
>> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2068)
>> at
>> org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:669)
>> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:462)
>> at
>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:214)
>> at
>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:179)
>> at
>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>> at
>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
>> at
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>> at
>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
>> at
>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
>> at
>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
>> at
>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
>> at
>> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>> at
>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
>> at
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>> at
>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
>> at
>> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.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.java:257)
>> at
>> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
>> at
>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
>> at
>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>>
>> -
>> Best regards
>> --
>> View this message in context: 
>> http://lucene.472066.n3.nabble.com/Json-facet-api-NullPointerException-tp4239900.html
>> Sent from the Solr - User mailing list archive at Nabble.com.

Re: Json facet api NullPointerException

2015-11-12 Thread Yago Riveiro

I found the bug …




In my query I have 




sort: index,




And should be




sort:{index:desc|asc}




I think that the json parser should raise a “json parsing error” ...


—/Yago Riveiro

On Thu, Nov 12, 2015 at 4:44 PM, Yago Riveiro 
wrote:

> Solr 5.3.1
> —/Yago Riveiro
> On Thu, Nov 12, 2015 at 4:21 PM, Yonik Seeley  wrote:
>> Thanks for the report Yago,
>> What version is this?
>> -Yonik
>> On Thu, Nov 12, 2015 at 10:53 AM, Yago Riveiro  
>> wrote:
>>> Hi,
>>>
>>> I'm hitting this NullPointerException using the json facet API.
>>>
>>> Same query using Facet component is working.
>>>
>>> Json facet query:
>>>
>>> curl -s http://node1:8983/solr/metrics/query -d
>>> 'q=datetime:[2015-10-01T00:00:00Z TO
>>> 2015-10-04T23:59:59Z]=0={
>>> urls: {
>>> type: terms,
>>> field: url,
>>> limit: -1,
>>> sort: index,
>>> numBuckets: true
>>> }}'
>>>
>>> Facet component query:
>>>
>>> http://node1:8983/solr/metrics/query?q=datetime:[2015-10-01T00:00:00Z%20TO%202015-10-04T23:59:59Z]=true=url=1=-1=0=json=1=index
>>>
>>> Total elements returned: 1971203
>>> Total unique elements returned: 307570
>>>
>>> Json facet api response:
>>>
>>> 2015-11-12 15:29:53.130 ERROR (qtp1510067370-34151) [c:metrics:shard1
>>> r:core_node5 x:metrics_shard1_replica2] o.a.s.s.SolrDispatchFilter
>>> null:java.lang.NullPointerException
>>> at
>>> org.apache.solr.search.facet.FacetFieldProcessorFCBase$1.lessThan(FacetField.java:573)
>>> at
>>> org.apache.solr.search.facet.FacetFieldProcessorFCBase$1.lessThan(FacetField.java:570)
>>> at
>>> org.apache.lucene.util.PriorityQueue.upHeap(PriorityQueue.java:258)
>>> at org.apache.lucene.util.PriorityQueue.add(PriorityQueue.java:135)
>>> at
>>> org.apache.solr.search.facet.FacetFieldProcessorFCBase.findTopSlots(FacetField.java:603)
>>> at
>>> org.apache.solr.search.facet.FacetFieldProcessorFCBase.getFieldCacheCounts(FacetField.java:547)
>>> at
>>> org.apache.solr.search.facet.FacetFieldProcessorFCBase.process(FacetField.java:512)
>>> at
>>> org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:222)
>>> at
>>> org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:313)
>>> at
>>> org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:57)
>>> at
>>> org.apache.solr.search.facet.FacetModule.process(FacetModule.java:87)
>>> at
>>> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:277)
>>> at
>>> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
>>> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2068)
>>> at
>>> org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:669)
>>> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:462)
>>> at
>>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:214)
>>> at
>>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:179)
>>> at
>>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>>> at
>>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
>>> at
>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>>> at
>>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
>>> at
>>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
>>> at
>>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
>>> at
>>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
>>> at
>>> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>>> at
>>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
>>> at
>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>>> at
>>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
>>> at
>>> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.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.java:257)
>>> at
>>> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
>>> at
>>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
>>> at
>>>

Re: Json facet api NullPointerException

2015-11-12 Thread Yonik Seeley

On Thu, Nov 12, 2015 at 11:48 AM, Yago Riveiro  wrote:
> In my query I have
> sort: index,
>
> And should be
>
> sort:{index:desc|asc}
>
> I think that the json parser should raise a “json parsing error” ...


Yeah, either that or "index" should be synonymous with "index asc".

-Yonik

Re: Search query speed

Re: fl=value equals?

Re: fl=value equals?

Re: Parent/Child (Nested Document) Faceting

Re: Parent/Child (Nested Document) Faceting

Re: Parent/Child (Nested Document) Faceting

Re: Parent/Child (Nested Document) Faceting

Json facet api NullPointerException

Re: Explicit commit with openSearcher=false

Re: Json facet api NullPointerException

Re: Json facet api NullPointerException

Re: Json facet api NullPointerException

Re: Json facet api NullPointerException

13 matches

Site Navigation

Mail list logo

Footer information