Changing Solr Types
Changing a Solr type mapper is rarely if ever done and is not recommended; however, for particular circumstances, such as converting the Solr LongField to TrieLongField, configure the dseTypeMappingVersion using the force option.
Changing a Solr type mapper is rarely if ever done and is not recommended; however, for particular circumstances, such as converting Solr types such as the Solr LongField to TrieLongField, you configure the dseTypeMappingVersion using the force option.
The Cassandra internal validation classes of the types you are converting to and from must be
compatible. Also, the actual types you are converting to and from must be valid types. For
example, converting a legacy Trie type to a new Trie type is invalid because corresponding
Cassandra validators are incompatible. The output of the CLI
command,
DESCRIBE
keyspace_name, shows the validation classes assigned to columns.
<dseTypeMappingVersion force = "true">1</dseTypeMappingVersion>
Use this option only if you are an expert and have confirmed that the Cassandra internal validation classes of the types involved in the conversion are compatible.
To use DSE Search data from a 3.0 release or earlier, use the legacy type mapping.