Unless you think we shouldn't
> bother doing anything drastic/sweeping (possibly breaking users) if it's
> likely we don't even want it?
>
Yeah that's the core of it. We could wind up breaking things twice.
--
http://www.needhamsoftware.com (work)
https://a.co/d/b2sZLD9 (my fantasy fiction book)
Welcome :)
On Mon, Dec 23, 2024 at 12:32 PM Christos Malliaridis <
c.malliari...@gmail.com> wrote:
> Welcome Pierre, looking forward to working with you. :)
>
> On Mon, Dec 9, 2024 at 10:23 AM Pierre Salagnac >
> wrote:
>
> > Thank you so much everyone!
> >
> > I am very excited to be invited to
I'm sympathetic to your questioning of NamedList's alleged performance
benefits (or even NamedList's very existence) but I don't see why that
would have any coupling to my proposal. Unless you think we shouldn't
bother doing anything drastic/sweeping (possibly breaking users) if it's
likely we don
Welcome Pierre, looking forward to working with you. :)
On Mon, Dec 9, 2024 at 10:23 AM Pierre Salagnac
wrote:
> Thank you so much everyone!
>
> I am very excited to be invited to join the community as a committer.
>
> I've been working with Solr for 10 years now, my first experience was with
>
> On Dec 23, 2024, at 8:20 AM, Gus Heck wrote:
>
> While we are at it, let's fix the cases that emit JSON objects with
> duplicate keys!
Oh, I kind of like that. Keeps the parsers honest. :-)
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
With respect to the effect on JSON output I'm for that. A single
dimensional Array encoding a 2D array to communicate key/value pairs is
very contrary to any programmer's expectations (at least within this
century). So improving the rendering of our JSON at some point: definitely
+1 While we are at
Welcome, Pierre!
On Tue, Dec 17, 2024 at 11:17 AM Alessandro Benedetti
wrote:
>
> Welcome on board Pierre!
> --
> *Alessandro Benedetti*
> Director @ Sease Ltd.
> *Apache Lucene/Solr Committer*
> *Apache Solr PMC Member*
>
> e-mail: a.benede...@sease.io
>
>
> *Sease* - Inf
The following tests are consistently failing for me.
- TestModelManagerPersistence.testModelAreStoredCompact
- TestModelManagerPersistence.testModelStorePersistence
- TestModelManager.loadModel_openAi_shouldLoadModelConfig
- TestModelManager.loadModel_huggingface_shouldLoadModelConfig
- TestModelM
Ultimately I'd love to see CBOR or a similar format supercede (and
eventually deprecate) javabin for both v1 and v2.
1. From early perf-testing it's supposedly already more efficient than
javabin (More thorough testing is always welcome)
2. CBOR is a popular format that can be parsed in languages
