Thanks Kevin.
I intend to move to the new HTTP2 classes but could not find an equivalent
of this code
HttpClientUtil.setHttpClientBuilder(new
Krb5HttpClientBuilder().getBuilder());
I was hoping someone could point me in the right direction.
Thank you
Rajiv Bandi
On Thu, Jan 5, 2023 at 12:22 A
Post processing on two fields means you might have to implement your own
pagination too instead of using facet.limit and facet.offset. Potentially
over millions of usernames. It also renders facet.mincount useless.
Thomas
Op wo 4 jan. 2023 om 18:59 schreef Mikhail Khludnev :
> Hello Julia,
> I'm
The deprecation came in as part of
https://issues.apache.org/jira/browse/SOLR-15223 (commit
https://github.com/apache/solr/commit/77921bab52f5)
The idea being to use the newer LBHttp2SolrClient and other classes instead
of the older HttpClient classes. In the short term using
Krb5HttpClientBuilder
Hello Julia,
I'm not sure why not just post process facet values of two fields. Overall,
JSON Facets are not extendable (btw, why?). To hack them you need to extend
FacetModule and inject your custom facet processor somewhere
around
org.apache.solr.search.facet.FacetParser#parseFacetOrStat(java.la
Hi Julia,
As I'm working with indexes that are updated infrequently and queried very
frequently, I would duplicate that data with copyField directives at index
time. Writing a custom facet processor comes with the risk that it might
break with a Solr upgrade.
Are you talking millions of unique us
It looks like
"debug":{ ... "parsedquery":"name:some", "parsedquery_toString":"name:some",
..
"QParser":"LuceneQParser", "filter_queries":["features:here"], "
parsed_filter_queries":["features:here"],
On Wed, Jan 4, 2023 at 3:41 PM Noah Torp-Smith wrote:
> Thanks again for your input, Mikhail. I
Hi everyone,
We have two multi-valued fields, both containing usernames, and we'd like to
compute the combined counts across both fields. For example, if we were to
facet on these two docs:
doc1: { field1: [user1, user2], field2: [user3, user4] }
doc2: { field1: [user1, user3], field2: [user2]
It looks like you are running version >= 8.10? iirc, replacing legacy
cache implementations with the up-to-date default impl
(solr.CaffeineCache) has fixed similar problems in the past (though I
can't at the moment find the thread/issue to reference).
Michael
On Wed, Jan 4, 2023 at 6:59 AM slly
Hi All,
Wish you all a very happy new year.
I am trying to upgrade my SolrJ client from 8.11 to 9.1 .
My usecase is to connect to a Kerberos authenticated SolR cluster.
I see that the current Krb5HttpClientBuilder class has been deprecated in
Solr 9.1
I am unable to find an updated 9.1 e
// from jdk1.8
"If the specified key is not already associated with a value, attempts to
compute its value using the given mapping function and enters it into this map
unless null. The entire method invocation is performed atomically, so the
function is applied at most once per key. Some a
Maybe this is a jdk “bug”, but it should be used incorrectly.
At 2023-01-04 19:58:35, "slly" wrote:
>Does anyone have similar problems?
>
>
>The cache class we configured is FastLRUCache in solrconfig.xml
>
>
>autowarmCount="0"/>
>
>
>Many threads are blocking the stack bel
Thanks again for your input, Mikhail. I need to look more into this debugOutput
and the way we use `!parent which`.
Can you maybe elaborate on which part of the debug output I should look at in
order to say "how is it parsed"? Is that output documented somewhere (other
than the solr source code
Does anyone have similar problems?
The cache class we configured is FastLRUCache in solrconfig.xml
Many threads are blocking the stack below:
"qtp2141817446-2744893" #2744893 prio=5 os_prio=0 tid=0x7f0b1b9f4800
nid=0x3ea9 waiting for monitor entry [0x7f0b16bdd000]
java.lang
13 matches
Mail list logo
