Are you using maven or gradle? You should just add
org.apache.solr
solr-solrj
8.8.2
looking at dependency tree I see there are a lot of jars added:
[INFO] +- org.apache.solr:solr-solrj:jar:8.7.0:compile
[INFO] | +- commons-io:commons-io:jar:
Ok thanks, I'll bear that in mind. I've raised
https://issues.apache.org/jira/browse/SOLR-15558 and will add a patch when
I have some free time
On Wed, 21 Jul 2021 at 15:56, Mike Drob wrote:
> That seems like a reasonable check to add, the only caution I would advise
> is that a lot of developer
On 7/21/2021 9:51 PM, Satya Nand wrote:
Hi Shawn,
Thank you, I also had my suspicion on the sow parameter. but I can't figure
out why it is acting differently for analyzed type and non-analyzed.
for example, If I give this query to solr 8.7
fq=negativeattribute:(citychennai mcat43120
20mcat431
I looked into this (https://solr.apache.org/guide/7_4/docvalues.html), and it
looks like I can't use docvalues because my field type is solr.textfield.
Specifically:
I'm passing in a string of tokens separated by '|'.
Some (made up) example data would be:
41654165|This i
I don't have any sort option configured. The score I'm getting back is 1.0
for each hit item.
Does anyone know about Lucene's internal functionality to help me
understand what the returned order is?
Steven
On Wed, Jul 21, 2021 at 10:52 AM Vincenzo D'Amore
wrote:
> if no sort options are confi
No sort option configured generally defaults to score (and currently does
so even in cases such as the "*:*" case (MatchAllDocsQuery) where sort is
guaranteed to be irrelevant; see:
https://issues.apache.org/jira/browse/SOLR-14765).
But functionally speaking that doesn't really matter: in the even
I dug some more into a workaround and found, the SortableTextField, field type:
https://solr.apache.org/guide/7_4/field-types-included-with-solr.html
My max length is 3945.
Any concerns about changing my solr.TextField type to a SortableTextField type
in order to enable docValues?
I would then
SortableTextField uses docValues in a very specific way, and is not a
general-purpose workaround for enabling docValues on TextFields. Possibly
of interest: https://issues.apache.org/jira/browse/SOLR-8362
That said, DocValues are relevant mainly (only?) wrt full-domain per-doc
value-access (e.g.,
ps- wrt requesting a "literal, complete search url" to aid troubleshooting:
facets, `sort`, `offset`, and `rows` params would all be of particular
interest.
On Thu, Jul 22, 2021 at 12:25 PM Michael Gibney
wrote:
> SortableTextField uses docValues in a very specific way, and is not a
> general-pu
On 7/22/2021 10:39 AM, Michael Gibney wrote:
ps- wrt requesting a "literal, complete search url" to aid troubleshooting:
facets, `sort`, `offset`, and `rows` params would all be of particular
interest.
One way to get everything we are after for the query is to add
"echoParams=all" to the quer
RE Shawn and Michael,
I am just looking for a way to speed it up. Mike Drob had mentioned docvalues,
which is why I was researching that route.
I am running my search tests from solr admin, no facets, no sorting. I am
using Dsolr.directoryFactory=HdfsDirectoryFactory
URL:
. /select?q=ptokens:
Thanks Shawn In our application I saw noggit.jar added so after removing it
now I could instantiate with the zk IP’s. thanks for the help
On Thu, 22 Jul 2021 at 8:54 AM, Shawn Heisey wrote:
> On 7/21/2021 6:37 PM, Reej Nayagam wrote:
> > I tried earlier with zk ensemble, but when i try to get th
Thanks Vincenzo D'Amore & Shawn
Hi Ours is a legacy system using EJB, no maven or graddle. And now I’m able
to instantiate passing zk ip’s after removing the noggit jar.
As suggested
On Thu, 22 Jul 2021 at 4:01 PM, Vincenzo D'Amore wrote:
> Are you using maven or gradle? You should just add
>
>
Classification: Confidential
Hi All,
I am using SOLR 7.5 Master/Slave architecture in my project. Just wanted to
know, is there any way in which we can print responses generated by SOLR query
in some log file i.e. as many solr query are getting hit, we can store the
response in some file.
If it
14 matches
Mail list logo
