[jira] [Commented] (SOLR-11358) Support DelimitedTermFrequencyTokenFilter-using fields with payload() function
[
https://issues.apache.org/jira/browse/SOLR-11358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479349#comment-16479349
]
Erik Hatcher commented on SOLR-11358:
-
{quote}Lets not bloat it?
{quote}
The default schema has dynamic field mapping for every language Solr supports
and bunch of other dynamic fields including the payload float/string/int ones.
Surely this one is ok to add too?
> Support DelimitedTermFrequencyTokenFilter-using fields with payload() function
> --
>
> Key: SOLR-11358
> URL: https://issues.apache.org/jira/browse/SOLR-11358
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Erik Hatcher
>Assignee: Erik Hatcher
>Priority: Major
> Attachments: SOLR-11358.patch
>
>
> payload() works values encoded with DelimitedPayloadTokenFilter. payload()
> can be modified to return the term frequency instead, when the field uses
> DelimitedTermFrequencyTokenFilter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11358) Support DelimitedTermFrequencyTokenFilter-using fields with payload() function
[ https://issues.apache.org/jira/browse/SOLR-11358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479250#comment-16479250 ] David Smiley commented on SOLR-11358: - bq. Coming back to this, and double-checking the test cases and implementation, I question whether this is really useful, to have `payload()` return the same value that `termfreq()` would. I agree with that; freq != payload! I'm not to keen on seeing advanced stuff getting added to the _default_ schema. Lets not bloat it? > Support DelimitedTermFrequencyTokenFilter-using fields with payload() function > -- > > Key: SOLR-11358 > URL: https://issues.apache.org/jira/browse/SOLR-11358 > Project: Solr > Issue Type: New Feature > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Erik Hatcher >Assignee: Erik Hatcher >Priority: Major > Attachments: SOLR-11358.patch > > > payload() works values encoded with DelimitedPayloadTokenFilter. payload() > can be modified to return the term frequency instead, when the field uses > DelimitedTermFrequencyTokenFilter. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11358) Support DelimitedTermFrequencyTokenFilter-using fields with payload() function
[
https://issues.apache.org/jira/browse/SOLR-11358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479196#comment-16479196
]
Erik Hatcher commented on SOLR-11358:
-
Coming back to this, and double-checking the test cases and implementation, I
question whether this is really useful, to have `payload()` return the same
value that `termfreq()` would.
At least let's add:
{{ }}
{{ }}{{ }}
{{ }}
{{ }}{{ }}
{{ }}{{
}}
{{ }}
to the default managed-schema.
I could see it being handy if you're testing the difference between *_dpi and
*_dtf performance and potentially toggling back and forth and want it to be
transparent, but these delimited tf fields aren't going to work as if they were
truly payloaded with the payload scoring queries currently.
Thoughts?
> Support DelimitedTermFrequencyTokenFilter-using fields with payload() function
> --
>
> Key: SOLR-11358
> URL: https://issues.apache.org/jira/browse/SOLR-11358
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Erik Hatcher
>Assignee: Erik Hatcher
>Priority: Major
> Attachments: SOLR-11358.patch
>
>
> payload() works values encoded with DelimitedPayloadTokenFilter. payload()
> can be modified to return the term frequency instead, when the field uses
> DelimitedTermFrequencyTokenFilter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
