Thanks Erick, that makes sense.
However it does lead me to another conclusion: in Solr prior to 6.0, or with
sow=true on Solr 6.0+ that would mean that the ShingleFilter is totally
ineffective within query analysers. It would be logically equivalent to not
having the ShingleFilter configur
One other question
Is there a system level configuration that can change the default for the sow=
parameter? Can it be flipped to have the default set to true?
Many Thanks,
Neil
On 22/03/2019, 08:36, "Hubert-Price, Neil" wrote:
Thanks Erick, that makes sense.
However it do
Hi,
I am trying to use LTR with solr 6.6.2.There are different types of model
like Linear Model, Multiple Additive Trees Model and Neural Network Model.
I have tried using Linear & Multiadditive model and compared the
performance of results. There is a major difference in response time
between th
Can you share the time needed of the two models? How many documents? What is
your loading pipeline? Have you observed cpu/memory?
> Am 22.03.2019 um 12:01 schrieb Kamal Kishore Aggarwal :
>
> Hi,
>
> I am trying to use LTR with solr 6.6.2.There are different types of model
> like Linear Model,
Hi all,
My solr query sometime taking more than 60 sec to return the response .
Is there any way I can check why it is taking so much time .
Please let me know if there is any way to analyse this issue(high
response time ) .Thanks
Should probably send this one from an anonymous email... :(
I can see from the results that elevate is working with this:
select?&defType=edismax&q=transcript&qf=my_field
However, elevate is not working with this:
select?&q={!edismax%20v=transcript%20qf=my_field}
This is Solr 4.x...y, I know..
On 3/22/2019 2:02 AM, Hubert-Price, Neil wrote:
One other question
Is there a system level configuration that can change the default for the sow=
parameter? Can it be flipped to have the default set to true?
Any parameter can be put into the query handler definition. In
defaults, inva
On 3/22/2019 7:52 AM, Rajdeep Sahoo wrote:
My solr query sometime taking more than 60 sec to return the response .
Is there any way I can check why it is taking so much time .
Please let me know if there is any way to analyse this issue(high
response time ) .Thanks
With the information pr
Range queries against mutivalued string fields produces useless highlighting,
even though "hl.highlightMultiTerm":"true"
I have uncovered what I believe is a bug. At the very lease it is a difference
in behavior between Solr v5.1.0 and v7.5.0 (and v7.7.1).
I have a Field defined in my schema as
This might be causing the high CPU in 7.7.x.
https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369f5188cdd5e3ae2b151434#diff-e54b251d166135a1afb7938cfe152bb5
That is related to this JDK bug
https://bugs.openjdk.java.net/browse/JDK-8129861.
Thanks
Jay Potharaju
On Thu, Mar 21, 2019
I think the issue is that you store the feature as originalScore but in
your model you refer to it as original_score
On Wed, Mar 20, 2019 at 1:58 PM Mohomed Rimash wrote:
> one more thing i noticed is your feature params values doesn't wrap in q or
> qf field. check that as well
>
> On Wed, 20
HI Jörn Franke,
Thanks for the quick reply.
I have performed the jmeter load testing on one of the server for Linear vs
Multipleadditive tree model. We are using lucidworks fusion.
There is some business logic in the query pipeline followed by main solr
ltr query. This is the total time taken by
12 matches
Mail list logo
