RE: Solr fact response strange behaviour

2020-02-03 Thread Kaminski, Adi
ginal Message- From: Mikhail Khludnev Sent: Thursday, January 30, 2020 8:35 AM To: solr-user Subject: Re: Solr fact response strange behaviour What's happen at AutoCompleteAPI.java:170 ? On Wed, Jan 29, 2020 at 9:28 PM Kaminski, Adi mailto:adi.kamin...@verint.com>> wrote

Re: Solr fact response strange behaviour

2020-01-29 Thread Mikhail Khludnev
ase.run(SocketProcessorBase.java:49) > [tomcat-embed-core-9.0.17.jar:9.0.17] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [?:1.8.0_201] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [?:1.8.0_201

Re: Solr fact response strange behaviour

2020-01-29 Thread Jason Gerlowski
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415) > [tomcat-embed-core-9.0.17.jar:9.0.17] > at > org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) > [tomcat-embed-core-9.0.17.jar:9.0.17] > at >

RE: Solr fact response strange behaviour

2020-01-29 Thread Kaminski, Adi
) [tomcat-embed-core-9.0.17.jar:9.0.17] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201] -Original Message- From: Jason Gerlowski Sent: Wednesday, January 29, 2020 5:40 PM To: solr-user@lucene.apache.org Subject: Re: Solr fact response strange behaviour Hey Adi, There was a separate JIRA

Re: Solr fact response strange behaviour

2020-01-29 Thread Jason Gerlowski
Mikhail Khludnev > Sent: Tuesday, January 28, 2020 9:14 AM > To: solr-user > Subject: Re: Solr fact response strange behaviour > > > > https://issues.apache.org/jira/browse/SOLR-11775 > > > > On Tue, Jan 28, 2020 at 10:00 AM Kaminski, Adi > mailto:adi.kamin...

RE: Solr fact response strange behaviour

2020-01-27 Thread Kaminski, Adi
Message- From: Mikhail Khludnev Sent: Tuesday, January 28, 2020 9:14 AM To: solr-user Subject: Re: Solr fact response strange behaviour https://issues.apache.org/jira/browse/SOLR-11775 On Tue, Jan 28, 2020 at 10:00 AM Kaminski, Adi mailto:adi.kamin...@verint.com>>

Re: Solr fact response strange behaviour

2020-01-27 Thread Mikhail Khludnev
t).longValue() ? > > -Original Message- > From: Mikhail Khludnev > Sent: Tuesday, January 28, 2020 8:53 AM > To: solr-user > Subject: Re: Solr fact response strange behaviour > > I suppose there's an issue, which no one ever took a look. > > https://lucene.472066.n3.nabble.

RE: Solr fact response strange behaviour

2020-01-27 Thread Kaminski, Adi
fact response strange behaviour I suppose there's an issue, which no one ever took a look. https://lucene.472066.n3.nabble.com/JSON-facets-count-a-long-or-an-integer-in-cloud-and-non-cloud-modes-td4265291.html On Mon, Jan 27, 2020 at 11:47 PM Kaminski, Adi wrote: > SolrJ client is u

Re: Solr fact response strange behaviour

2020-01-27 Thread Mikhail Khludnev
I suppose there's an issue, which no one ever took a look. https://lucene.472066.n3.nabble.com/JSON-facets-count-a-long-or-an-integer-in-cloud-and-non-cloud-modes-td4265291.html On Mon, Jan 27, 2020 at 11:47 PM Kaminski, Adi wrote: > SolrJ client is used of SolrCloud of Solr 8.3 version for

Re: Solr fact response strange behaviour

2020-01-27 Thread Kaminski, Adi
SolrJ client is used of SolrCloud of Solr 8.3 version for JSON Facets requests...any idea why not consistent ? Sent from Workspace ONE Boxer On Jan 27, 2020 22:13, Mikhail Khludnev wrote: Hello, It might be different between SolrCloud and standalone mode. No data enough to make a conclusion.

Re: Solr fact response strange behaviour

2020-01-27 Thread Mikhail Khludnev
Hello, It might be different between SolrCloud and standalone mode. No data enough to make a conclusion. On Mon, Jan 27, 2020 at 5:40 PM Rudenko, Artur wrote: > I'm trying to parse facet response, but sometimes the count returns as > Long type and sometimes as Integer type(on different

Solr fact response strange behaviour

2020-01-27 Thread Rudenko, Artur
I'm trying to parse facet response, but sometimes the count returns as Long type and sometimes as Integer type(on different environments), The error is: "java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long" Can you please explain why this happenes? Why it not