Thank you for accepting my proposal -- I definitely volunteer to implement
it!
ETA: I've started... I should have a PR to share this weekend.
One thing I want to point out that I see is that, as tempting as it may be,
all the places inside Solr that call the existing Http1 (using Apache
HttpCli
Thank you both for the effort you’ve put in and will put in!
On Thu, Mar 17, 2022 at 12:11 PM Anshum Gupta
wrote:
> Thank you, Jan for all the effort and for serving as the chair.
>
> Congratulations and good luck, Houston!
>
>
>
> On Thu, Mar 17, 2022 at 6:14 AM Jan Høydahl wrote:
>
>> Hi,
>>
Sure that makes sense ... was just thinking the Log4J CVE would
warrant a change here but easy enough for people to upgrade the image!
On Thu, Mar 17, 2022 at 10:08 AM Houston Putman wrote:
>
> Unfortunately that would require a re-spin. We are going to start using the
> official SVN releases as
Thank you, Jan for all the effort and for serving as the chair.
Congratulations and good luck, Houston!
On Thu, Mar 17, 2022 at 6:14 AM Jan Høydahl wrote:
> Hi,
>
> It's been an honour to serve as chair for the Apache Solr PMC (Project
> Management Committee) for the last year. Quite a busy y
Hy,
I have a problem with my Solr database. I have a core with around 50 millions
documents (split in 4 shards) and it's extremely slow.
It takes around 50 seconds for 1000 new documents to be committed and I
frequently get this error:
Task queue processing has stalled for 20195ms with 0 remaini
To wrap up:
David's proposal:
* Un-deprecate CloudSolrClient to use it as the main cluster client going
forward
* Rename CloudSolrClient -> CloudHttp1SolrClient and rename BaseCloudSolrClient
-> CloudSolrClient
* Make a new Builder that will instantiate a CloudSolrClient instance with a
LBHttp2
Unfortunately that would require a re-spin. We are going to start using the
official SVN releases as the official helm chart location soon (which is a
major win, but we can't really go and change things after the fact anymore).
The default version is upgraded to 8.11 on main (v0.6.0), but I decide
+1 (binding)
Ran the smoke tester and deployed on Docker Desktop.
BTW: Is it possible to change the Solr version deployed from the Helm
chart to 8.11.1 w/o a respin of the RC? It's still deploying Solr 8.9
(easy enough to upgrade the Docker image if not)
Cheers,
Tim
On Wed, Mar 16, 2022 at 12:0
I think it's fine to change the SolrJ code in 9.0, it's a major version and
we are not doing it for a silly reason.
As long as we document the changes well (maybe we need a separate page for
Major changes in SolrJ-9), I don't see a reason why we can't make these
changes.
It could be that we shoul
Thanks Jan!
Thank you so much for all of the hard work you have done over the past year.
It's been an important, but difficult, year and we have been lucky to have
you at the helm!
I'm really excited for the next year and to see how far Solr is able to go
by the time I "leave office".
Please don'
Hi,
It's been an honour to serve as chair for the Apache Solr PMC (Project
Management Committee) for the last year. Quite a busy year for the project!
We have a tradition to rotate the role among PMC members, and the PMC has
elected Houston Putman as the next Solr Chair.
Congrats Houston, and
One simple solution is to revert SOLR-15223 Deprecate HttpSolrClient and
friends in 9.0, do the 9.0 release and then continue planning for the next-gen
Cloud client.
It could be that we should be even bolder in 10.0 and provide a more modern
Cluster SolrJ client that supports an instant pub/sub
12 matches
Mail list logo
