You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Weijie Wang (Jira)" <ji...@apache.org> on 2019/08/30 20:41:00 UTC
[jira] [Created] (SOLR-13730) payload text is parsed in a backward
order
Weijie Wang created SOLR-13730:
----------------------------------
Summary: payload text is parsed in a backward order
Key: SOLR-13730
URL: https://issues.apache.org/jira/browse/SOLR-13730
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Components: query parsers
Affects Versions: 8.2
Reporter: Weijie Wang
I followed [this|[https://lucidworks.com/post/end-to-end-payload-example-in-solr/]] to add a payload field for my solr schema and find out that DelimitedPayloadTokenFilter used to parse payload input is parsing it in a backward order, which will let it always find the first delimiter ('|' in my case) to split on, which will result in parsing error for inputs like "abc|def|0.5" (`def|0.5` is not a float). And it makes sense if my key for this payload happen to contain a '|'. Is it possible to change it to split on the last delimiter or provide an option for this as the sub-string after the last delimiter is guaranteed to be a payload score?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org