Thanks, David Smiley and Gus Heck for this wonderful insight.
On Thu, Mar 16, 2023 at 3:46 AM Gus Heck wrote:
> I think I recall past experience that if the ID is duplicated, you get one
> or the other, and the one you get is non-deterministic, but as this is an
> unsupported and untested config
Ah, Solr wants a Codec*Factory* whereas you supplied the class name of the
Codec.
And of course your codec is a WIP I assume; you didn't customize the stored
fields to not use compression yet.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Mar
I tested "streaming expressions" ('expr=search(test_collection,q="*:*",fl="id, text_sn",sort="id asc",rows=1600)') on collection with one shard with small documents - a long preparation of the server response before the data transfer begins (it looks like when the collection consisted of 8 shar
Thanks for the reminder Jan, it is now merged and backported!
- Houston
On Sat, Mar 18, 2023 at 6:51 PM Jan Høydahl wrote:
> Remember to merge https://github.com/apache/solr/pull/1436
>
> I can do it if you wish but it ties in with other changes syncing I guess.
>
> Jan Høydahl
>
> > 18. mar. 2
Why do you think the IntelliJ "Google Java Format" plugin will start
changing formats beyond what Spotless is doing? Spotless uses GJF :-).
Okay there's more to it than that... I recall the IntelliJ plugin variant
also honors some Java import statement order stuff but the Spotless plugin
doesn't.
Thanks for moving this along! This is a good step in the right direction.
I hope that we get more source code validation at some point so that we don't
need to constantly remind folks "We follow the Google Java Format" ;-).
One thought…. If I set my IntelliJ to use the
https://plugin
It does appear that the logs are being truncated by the logger:
https://logging.apache.org/log4j/log4j-2.8/log4j-core/apidocs/org/apache/logging/log4j/core/pattern/MaxLengthConverter.html
.
But, I've created a ticket to selectively suppress certain parameters in
the logs:
https://issues.apache.or
I've run into an issue with KNN vector queries and the Solr logs. The issue
is for large vectors you can end up with 20K+ of just vector data in the
logs. This is because each floating point value in the vector can take 20+
characters to express as a string. In our testing the log line is getting
t
