a default similarity added as ctor param
> SchemaSimilarityFactory should delegate queryNorm and coord to the default
> similarity
> -
>
> Key: SOLR-9315
> URL: htt
[
https://issues.apache.org/jira/browse/SOLR-9315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand closed SOLR-9315.
--
Resolution: Duplicate
> SchemaSimilarityFactory should delegate queryNorm and coord to the defa
[
https://issues.apache.org/jira/browse/SOLR-9315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392295#comment-15392295
]
Adrien Grand commented on SOLR-9315:
Yes Uwe, both queryNorm and coords are gon
Solr. The problem exists there, too.
I agree, for the coord factor its no longer needed in master. Is queryNorm also
gone in master?
> SchemaSimilarityFactory should delegate queryNorm and coord to the default
>
bout committing it?
I'm happy to commit it, but I wouldn't know how to provide a test for it.
> SchemaSimilarityFactory should delegate queryNorm and coord to the default
> similarity
> -
>
&
ince coord and queryNorm are gone from
master.
> SchemaSimilarityFactory should delegate queryNorm and coord to the default
> similarity
> -
>
> Key: SOLR-9315
>
[
https://issues.apache.org/jira/browse/SOLR-9315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated SOLR-9315:
---
Attachment: SOLR-9315.patch
Here is a proposed change that delegates coord and queryNorm to the
: SchemaSimilarityFactory can easily build similarities that apply
the idf twice.
> SchemaSimilarityFactory should delegate queryNorm and coord to the default
> similarity
> -
>
> Key: SOLR-9315
>
Adrien Grand created SOLR-9315:
--
Summary: SchemaSimilarityFactory should delegate queryNorm and
coord to the default similarity
Key: SOLR-9315
URL: https://issues.apache.org/jira/browse/SOLR-9315
[
https://issues.apache.org/jira/browse/LUCENE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-7347.
--
Resolution: Fixed
Fix Version/s: master (7.0)
Both queryNorm and coords are now gone in
[
https://issues.apache.org/jira/browse/LUCENE-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-7368.
--
Resolution: Fixed
> Remove queryNorm
>
>
> Key:
7368:
-
Commit 5def78ba101dd87261c787dc865979769c4b58e4 in lucene-solr's branch
refs/heads/master from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5def78b ]
LUCENE-7368: Remove queryNorm.
> Remove queryNorm
>
>
>
. Instead,
boost are passed to Weights and stats at construction time. It helps have more
final fields and simplifies BoostQuery. The boost is now a simple
multiplicative factor, it can't get normalized away by the query norm like it
used to happen with ClassicSimilarity.
> Remove q
Adrien Grand created LUCENE-7368:
Summary: Remove queryNorm
Key: LUCENE-7368
URL: https://issues.apache.org/jira/browse/LUCENE-7368
Project: Lucene - Core
Issue Type: Sub-task
e some
other param.
Any way, if you guys really think we're better off without coord then I'm not
standing in your way. Seems a shame to see it go, though.
> Remove queryNorm and coords
> ---
>
> Key: LUCENE-7347
>
naturally get a better score than the first document with 1000
x's and 0 y's.
> Remove queryNorm and coords
> ---
>
> Key: LUCENE-7347
> URL: https://issues.apache.org/jira/browse/LUCENE-7347
> Project
e relationship between term saturation and coord.
Obviously if we remove features, it's easier to maintain the codebase and may
make optimizations easier :-) That goes without saying.
> Remove queryNorm and coords
> ---
>
> Key: LUCENE-73
ault Similarity anymore and that BM25, which I
see as a better TF-IDF, does not need them, I think it is appealing to remove
them so that we can make the code for boolean queries easier to read and less
bug-prone.
> Remove queryNorm and coords
> ---
>
>
ng models, especially when
this clinging holds back important improvements, e.g. {{BooleanQuery}} could do
more aggressive rewriting if its hands were not tied by coord.
> Remove queryNorm and coords
> ---
>
> Key: LUCENE-7347
>
e to TF-IDF? It seems like a universal
concept that isn't intrinsically tied to specific scoring formulas -- i.e. I
could extend any Similarity and override coord() to my liking. I'd hate to see
it go.
> Remove queryNorm and coords
> ---
>
>
[
https://issues.apache.org/jira/browse/LUCENE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339223#comment-15339223
]
Michael McCandless commented on LUCENE-7347:
+1
> Remove queryN
[
https://issues.apache.org/jira/browse/LUCENE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-7347:
-
Summary: Remove queryNorm and coords (was: Remove queryNorm and
disableCoord)
> Rem
Adrien Grand created LUCENE-7347:
Summary: Remove queryNorm and disableCoord
Key: LUCENE-7347
URL: https://issues.apache.org/jira/browse/LUCENE-7347
Project: Lucene - Core
Issue Type
[
https://issues.apache.org/jira/browse/LUCENE-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Barry updated LUCENE-4559:
---
Summary: PerFieldSimilarityWrapper issue with queryNorm() and coord()
(was
Is it possible to remove the QueryNorm??
so all the bf boost became an add of the solr score??
omitNorm is about fieldNorm or queryNorm??
thanx
--
Gastone Penzo
Hello,
someone can explain the difference between queryNorm and FieldNorm in
debugQuery??
why if i push one bf boost up, the queryNorm goes down??
i made some modifies..before the situation was different. why??
thanx
--
Gastone Penzo
.com]
[Parenting|http://childcareforums.com]
> Modify confusing javadoc for queryNorm
> --
>
> Key: LUCENE-1896
> URL: https://issues.apache.org/jira/browse/LUCENE-1896
> Project: Lucene - Java
27 matches
Mail list logo
