I did start start with this but it's a limited approach since it only works
with text fields. Right now I'm using this with a bunch of custom fields
extended to support payloads but that is expensive to maintain between
versions, especially when APIs change so I'm looking for a less invasive
way
Have you tried starting with the DelimitedPayloadTokenFilterFactory?
There is a sample configuration in the shipped examples:
https://github.com/apache/lucene-solr/blob/releases/lucene-solr/6.1.0/solr/example/example-DIH/solr/db/conf/managed-schema#L625
Regards,
Alex.
Newsletter and
Ok, did a bit more digging. It looks like if I build a custom
ContentStreamLoader I can create a custom AddOrUpdateCommand that is
ultimately responsible for building the lucene document. So looks like if
I build a custom UpdateRequestHandler I can register my custom
ContentStreamLoader and I'll
I have a need to build custom field types that store additional metadata at
the field level in a payload. I was thinking that I could satisfy this by
building a custom UpdateRequest that captured this additional information
in XML, but I am not really sure how to get at this additional
