Hi folks,
For reasons not to be discussed I am stuck with the combination JDK 8 and Solr
8.11.2. Everything looks good as long as I use JDK 1.8.0_351 but Solr won't
start properly as soon as I switch to JDK 1.8.0_361 and solr.log file contains
a Java stack trace with e.g. this particular entry
FYI,
https://issues.apache.org/jira/browse/SOLR-16682 MLT component:
SyntaxError: Cannot parse
has been committed. It should be released at 9.2
On Fri, Dec 2, 2022 at 7:00 PM Wu, Hansen [USA] wrote:
> Hi Alessandro and Mikhail,
> Thanks for your tips first.
> I discussed with my team about esca
Thank you.
I have corrected the time and I don't see the error as such.
On Sun, Feb 26, 2023 at 6:07 PM Thomas Corthals
wrote:
> Hi Hari
>
> Are the clocks on both the server and the client running correctly? My
> guess is that one of them has drifted by more than 15 seconds.
>
> Thomas
>
> Op z
Hi Derek,
On Wed, Mar 1, 2023 at 2:43 AM Derek C wrote:
> Hi all,
>
> I have 5 copies/replicas of a SOLR collection with SOLR Cloud & Zookeeper
> (SOLR 9.0)
>
> I'm trying to get to the bottom of a strange issue: Documents that are
> updated
> with queries to a single SOLR server/endpoint get r
Hi Geren,
Sorry about the initial response, I just looked over your expression and
didn't read the full context. I've experienced similar behavior when I've
deviated (unintentionally) from the documentation. I think it's worth
raising a JIRA, SEs can definitely benefit from better error
respo
Hi Derek,
I'm not sure how your image embeddings were generated, but as you probably
know, I think it is only by experiment in each case that you can determine
how far you can reduce the dimensions and/or compress the encoding values
of each dimension before too-detrimental effects on nearest-neig
Hi all,
I have 5 copies/replicas of a SOLR collection with SOLR Cloud & Zookeeper
(SOLR 9.0)
I'm trying to get to the bottom of a strange issue: Documents that are
updated
with queries to a single SOLR server/endpoint get replicated across all
replicas in the cluster (as you'd expect) and this i
Hi Kent,
That's very interesting. We have been thinking about reducing,
down-scaling, our dense vectors from 512 to 64 perhaps using PCA.
We have about 2.5 million documents and we did some testing (with Apache
JMeter) and after about 10 concurrent requests we start
to have performance problems (
Yea sorry the question was if that's a bug and if it should throw an error?
The results right now are pretty confusing and I could see it leading to
some bugs.
On Mon, Feb 27, 2023 at 5:23 PM t sornin wrote:
> Your join key is reversed. It should be "on=item_id_2=item_id" which only
> returns t
Have you looked at
https://solr.apache.org/guide/8_11/faceting.html#limiting-facet-with-certain-terms
Is something like *facet.field={!terms='user1,user2'}field1* what you want?
- Andy -
On Tue, Feb 28, 2023 at 3:36 AM Deepak Michael
wrote:
> Hi
>
> I have a muti-valued field, containing usern
This is one of the few remaining feature gaps (afaik) between legacy
facets and JSON facets. There's.a relevant Jira issue
(https://issues.apache.org/jira/browse/SOLR-14921) that summarizes the
state of things pretty well, including what I think would be a
workaround for your case (if a bit verbose
Hello, Deepak.
Old facets also has related parameters facet.excludeTerms, .facet.contains,
facet.matches. but these are not fully fit to the problem.
JSON Facets are not easy to extendable. Presumably it may be done by
implementing extended FacetModule and deploying as a component plugin.
On Tue,
Nope: never trust noone, you know.
Make an account for you, check the mail please.
On Tue, Feb 28, 2023 at 5:17 AM Rajani Maski wrote:
> Thank you, appreciate it. I will follow along on the jira for a solution
> and workaround if any.
> Can I create a jira account myself?
>
>
> On Sat, Feb 25, 2
All,
I see warnings in the Solr master replication like this
2023-02-24 18:10:40.964 WARN (qtp156856360-13173) [
x:Fred_apis_responses_index] o.a.s.h.ReplicationHandler Exception while writing
response for params:
generation=394103&qt=/replication&file=segments_8g3b&checksum=true&compressio
Hi
I have a muti-valued field, containing usernames, that I want to facet on, but
I only want facets on a sub-set of those usernames.
For example, if I have these docs
doc1: { field1: [user1, user2, user4] }
doc2: { field1: [user1, user3, user5], }
doc3: { field1: [user3, user4, user6], }
I'd l
15 matches
Mail list logo
