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 <w2...@gmail.com> on 2019/08/30 20:55:56 UTC
payload text is parsed in a backward order
I followed https://lucidworks.com/post/end-to-end-payload-example-in-solr/ to
add a payload field for my solr schema and found out that the
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?
Many thanks,
W