+1 on deprecating bin/post. I haven't used it in many years either.
On Tue, May 23, 2023 at 7:30 PM Joel Bernstein wrote:
> I have mixed feelings about this because I love command line tools. But I
> haven't actually used the bin/post tool in years.
>
>
>
> On Tue, May 23, 2023 at 10:13 AM David
I have mixed feelings about this because I love command line tools. But I
haven't actually used the bin/post tool in years.
On Tue, May 23, 2023 at 10:13 AM David Smiley wrote:
> +1 to deprecate bin/post.
>
> Eric, RE the issue title... it's better. Still, if I were advocating for
> the work
Hello, Joel.
Here's my idea
https://lists.apache.org/thread/6t45p5fk4hldrt1833kvrbobdd2pk265
On Tue, May 23, 2023 at 6:20 PM Joel Bernstein wrote:
> One of the things that I'm focusing on is combining the Solr similarity
> score with the vector score in a consistent manner. My main concern is
One of the things that I'm focusing on is combining the Solr similarity
score with the vector score in a consistent manner. My main concern is
dealing with the unbounded nature of the Solr similarity score and how to
balance that with a vector score.
So my first question are there any mechanisms n
+1 to deprecate bin/post.
Eric, RE the issue title... it's better. Still, if I were advocating for
the work (and I'm definitely not), I'd have a dedicated issue nonetheless,
may or may not even have a separate Windows issue if it gets fixed by side
effect of moving the functionality.
~ David Smi
I say this despite the fact I know it will break some folks because anyone
relying on post.jar for a non-trivial use case will either have such a
horrible experience that they eventually move to elastic/opensearch or they
will write their own code anyway. The harm to future users is heavier.
On Tu
I know of divisions of very large companies that have specifically done
this, and even a product that wrote their "integrate with solr" suggesting
to use post.jar and then sold to customers saying that they supported solr
integration.
post.jar should die. The "stream a large file" use case should
Collection naming discussions that I recall were probably more than 24
months ago. One good strategy is git blame in the relevant code. That
should lead you to a commit hash and a commit message. The message would
mention the Jira ticket. The jira ticket would hopefully have discussion,
sometimes (
Hello Team,
In previous Solr versions, afaik examples post tool did not support
Kerberos (have not checked Solr 9.x), so each time a customer asked about
the Apache Solr tutorial I recommended them to use curl command as it works
with/without kerberos (curl --negotiate ). There are some curls
Wouldn’t it be cool if SolrCLI used Graal under the covers?
One thing about the various bin/solr tools that folks mentioned was that they
can be handy when you have complex auth scenarios, and that they can support
these natively. One thing I’d like to see in the future is to have all the
com
Lots of feedback!
So, would renaming SOLR-6994 from "Implement Windows version of bin/post" to
“Implement Windows version of bin/post via implementing bin/solr post” address
your concern David?
It’s both for Solr technical simplicity, but also to let Window’s users
actually have better s
11 matches
Mail list logo
