Re: Include JSON facet inside Solr Streaming

Is it possible to do a Join (Eg: hashJoin, innerJoin) on the facet stream expression? Regards, Edwin On 1 July 2017 at 03:30, Susheel Kumar wrote: > I doubt it can work. Why not utilise facet stream expression which use > JSON facet under the cover. > > On Thu, Jun 29, 2017 at 9:44 PM, Zheng L

Re: Not highlighting "and" and "or"?

Created Wish SOLR-10992 . Maybe I am a troublemaker, the example configs will need to be tested after the change is made and that will be a bother. Any tips on how to easily do that? Thanks Rick On 2017-06-30 10:54 AM, Walter Underwood wrote

Re: Include JSON facet inside Solr Streaming

I doubt it can work. Why not utilise facet stream expression which use JSON facet under the cover. On Thu, Jun 29, 2017 at 9:44 PM, Zheng Lin Edwin Yeo wrote: > Hi, > > Is it currently possible to include JSON facet inside Solr Streaming? > > I am trying out with the following query, which comb

RE: [EXTERNAL] - Re: custom search component process method not called

: It works ok for me now. Both cores execute as expected. : The ${solr.core.name} resolves correctly for both cores. As in I get the right name for each. Is still something I shouldn't do? No -- you're fine. That property is implicitly defined for all Solr cores, precisely for the type of

RE: [EXTERNAL] - Re: custom search component process method not called

It works ok for me now. Both cores execute as expected. The ${solr.core.name} resolves correctly for both cores. As in I get the right name for each. Is still something I shouldn't do? -S -Original Message- From: Chris Hostetter [mailto:hossman_luc...@fucit.org] Sent: Friday, June 3

RE: [EXTERNAL] - Re: custom search component process method not called

Sigh. Best way to find a stupid mistake is post it. I had this... explicit 10 saveStateComponent Instead of this explicit 10 saveStateComponent mailto:erickerick...@gmail.com] Sent: Friday, Jun

Re: custom search component process method not called

: : I believe the init bit is called on startup, so that leaves the second : part of your puzzle. I find this a bit suspicious though: : :${solr.core.name} : : Are you sure this is different for all three cores? My thought is that : the component is being called for all three cores but it's

Re: Same score for different length matches

: we have multiple documents that are matches for the query in question : ("name:hubwagen"). Thing is, some of the documents only contain the : query, while others match 100% in the "name" field: ... : 5.9861565 = (MATCH) weight(name:hubwag in 8093) [DefaultSimilarity], : result of: : 5.9

Re: custom search component process method not called

I believe the init bit is called on startup, so that leaves the second part of your puzzle. I find this a bit suspicious though: ${solr.core.name} Are you sure this is different for all three cores? My thought is that the component is being called for all three cores but it's hard to see b/c t

custom search component process method not called

I have a custom search component that registered in the last-components list for /select. The component does some bookkeeping. I got it working using a helloworld core using one of the example datasets. I have a few logging statements to monitor the custom processing. I have the jar with my c

Re: cursorMark / Deep Paging and SEO

Hi Jacques, this should satisfy your curiosity [1]. The mark is telling you the relative position in the sorted set ( and it is mandatory to use the uniqueKey as tie breaker). If you change your index, the query using an old mark should still work (but may potentially return different docuements if

Re: Not highlighting "and" and "or"?

I would agree with removing the stopword filter from the example configs. It is not a “best practice” or even a recommended practice. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jun 29, 2017, at 8:01 PM, Rick Leir wrote: > > Walter, Erick, Dav

Same score for different length matches

Hey, we have multiple documents that are matches for the query in question ("name:hubwagen"). Thing is, some of the documents only contain the query, while others match 100% in the "name" field: Hochhubwagen 5.9861565 Hubwagen 5.9861565 The debug looks like this (for the first and 5th

Re: Allow Join over two sharded collection

How many documents you have currently and how much it will be after growing drastically. Either you can add hardware and keep one shard until the joins are fully available or You can shard and distribute using composite id router and that's still better even though some/one shard(s) may get high l

cursorMark / Deep Paging and SEO

Hi Guys I'm not quite sure I understand the deep paging / cursorMark internals We have implemented it on our search pages like so: http://mysite.com/search?foobar&page=1 http://mysite.com/search?foobar&page=2&cmark=djkldskljsdsa http://mysite.com/search?foobar&page=3&cmark=uoieuwqjdlsa So if we