Update request processor (URP) and field transformer (FIT)
DataStax Enterprise (DSE) recommends using a field input/output transformer (FIT) API.
A field input/output transformer, an alternative for handling update requests, is executed later than a URP at indexing time. See the DataStax Developer Blog post An Introduction to DSE Field Transformers.
The DSE custom URP implementation is discouraged because it is almost always unnecessary.
DSE custom URP provided similar functionality to the Solr URP chain, but appeared as a plugin to Solr. The classic URP is invoked when updating a document using HTTP and the custom URP is invoked when updating a table using DSE. If both classic and custom URPs are configured, the classic version is executed first. The custom URP chain and the FIT API work with CQL and HTTP updates.
- Field input/output (FIT) transformer API
Steps to use the field input/output transformer API as an option to the input/output transformer support in Apache Solr™.
- FIT transformer class examples
Field input and output transformer (FIT) class examples.
- Custom URP example
The custom update request processor (URP) extends the Apache Solr™ URP.
- Interface for custom field types
CustomFieldTypeinterface marks Apache Solr custom field types and provides their actual stored field type.