I just checked Jenkins
https://builds.apache.org/job/Solr/job/Solr-Check-main/lastBuild/console and
noticed that the BATS tests appear to be failing. Judging from the error
message, we have some Solr processes running that aren’t getting cleaned up
properly.. Even by the test_zz_cleanup.bats
> Personally I think Confluence (in-place) is fine. Maybe start this way
> because it's simple & adequate?
+1 I think the simplest option is best for getting started, and then
we can iterate from there if we find Confluence lackluster, etc.
Best,
Jason
On Mon, Oct 16, 2023 at 10:42 PM David
Thanks for volunteering Alejandro. Option 1 works for me.
Ping me here or on Slack if you run into any permission issues (in
Confluence, Meetup.com, etc.) getting things setup for the meetup;
happy to help!
> eating your own dogfood kind of competitions
I really like the idea! Though I agree w
I’m really looking forward to these coming out (in whatever form) on a regular
basis ;-).
> On Oct 17, 2023, at 7:06 AM, Jason Gerlowski wrote:
>
>> Personally I think Confluence (in-place) is fine. Maybe start this way
>> because it's simple & adequate?
>
> +1 I think the simplest option
+1 (binding)
I ran the smoke tests:
> Successfully smoke tested the Solr Operator v0.8.0!
I also ran the end-to-end integration tests with the RC docker image and
Solr 9.4 and 8.11
$ make e2e-tests OPERATOR_IMAGE=apache/solr-operator:v0.8.0-rc1
> SOLR_IMAGE=solr:9.4
...
Hello Team,
Glad to be able to help. :-)
@Jason, I confirm I can now edit Solr's wiki. I just created the next
meeting notes.
I will add the newsletter section to Solr's wiki with Jason and David's
comments later today.
I spent some time during Solr Navigator presentation at the Solr Hackathon
to
Hi all,
I'm noticing an issue where rerank queries never appear to enter the Solr
queryResultCache
You can notice this, as a user, by simply repeating requests to a node.
You'll get an instantaneous response repeating most Solr queries. However,
repeating anything with rq= added, each response ta
My google-fu got better -- FWIW This looks like an issue fixed in the
normal rerank query code, but not in LTR, which is a different query parser
/ query path?
https://issues.apache.org/jira/browse/SOLR-7689
On Tue, Oct 17, 2023 at 4:03 PM Doug Turnbull
wrote:
> Hi all,
>
> I'm noticing an issu
On Tue, Oct 17, 2023 at 1:01 PM Arrieta, Alejandro <
aarri...@perrinsoftware.com> wrote:
>
> Editing: I agree with David's comments.
> I would add only one thing. The September edition is finished/over unless
> something is wrong with it and needs to be fixed. Draft or not draft that
> is the Sep
Question: Does the _version_ field have a purpose other than for "atomic
updates"?
I know SolrCloud and/or having an UpdateLog insists on it. But I don't
know if it's for that feature alone, or for additional non-obvious internal
workings of SolrCloud. Mostly I'm just asking to have a deeper
unde
To ensure reordered updates are processed properly from leader to other
replicas in NRT replication mode.
On Wed, 18 Oct, 2023, 9:55 am David Smiley, wrote:
> Question: Does the _version_ field have a purpose other than for "atomic
> updates"?
> I know SolrCloud and/or having an UpdateLog insist
I think the core use case for it is optimistic concurrency
https://solr.apache.org/guide/solr/latest/indexing-guide/partial-document-updates.html#optimistic-concurrency
On Wed, Oct 18, 2023 at 12:25 AM David Smiley wrote:
> Question: Does the _version_ field have a purpose other than for "atomi
Also DBQs use the version field to ensure they are applied correctly, even
if a DBQ is reordered
On Wed, 18 Oct, 2023, 10:05 am Ishan Chattopadhyaya, <
ichattopadhy...@gmail.com> wrote:
> To ensure reordered updates are processed properly from leader to other
> replicas in NRT replication mode.
>
The primary reason is as Ishan says - so that update reorders from leader
to replica can be handled in both normal and failure cases.
It’s also true that a part of the reason that the per document, NRT design,
with versions, was chosen was a desire to support per document optimistic
concurrency.
Fyi, SOLR-5944, is unreadable, but introduced the concept of previous
version or something like that.
On Wed, 18 Oct, 2023, 10:35 am Mark Miller, wrote:
> The primary reason is as Ishan says - so that update reorders from leader
> to replica can be handled in both normal and failure cases.
>
> I
Hello Team,
> I'm not very comfortable over-publicizing what I view as a first draft of
>the first edition.
Sure, no problem. Nothing shared.
>What is 10-20-30 about?
The number of news/links available for that newsletter. We need to decide
on the minimum news (non-relevant, like a new release) t
16 matches
Mail list logo
