Re: Search query speed

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

Re: fl=value equals?

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

Re: fl=value equals?

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,

Re: Parent/Child (Nested Document) Faceting

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,

Re: Parent/Child (Nested Document) Faceting

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,

Re: Parent/Child (Nested Document) Faceting

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

Re: Parent/Child (Nested Document) Faceting

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

Json facet api NullPointerException

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,

Re: Explicit commit with openSearcher=false

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

Re: Json facet api NullPointerException

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

Re: Json facet api NullPointerException

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

Re: Json facet api NullPointerException

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

Re: Json facet api NullPointerException

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