Configuring the Solr type mapping version

The Solr type mapping version defines how Solr types are mapped to Cassandra Thrift or Cassandra types.

The Solr type mapping version defines how Solr types are mapped to Cassandra Thrift or Cassandra types, and plays an important role in upgrades too. While DataStax Enterprise 3.0 used a simplified type mapping, also known as legacy mapping, or version 0, DataStax Enterprise 3.1 introduced a more accurate type mapping with version 1.

During and after upgrades from 3.0.x to 3.1.x or 3.2.x to 4.0, tables created with DataStax Enterprise 3.0.x requires legacy mapping, while new tables created with DataStax Enterprise 3.1.x and 3.2.x can use type mapping version 1.

DataStax Enterprise 3.2 introduced a new type mapping, known as version 2 type mapping, to model the latest CQL 3 changes. Tables migrated from previous DataStax Enterprise installations can keep the old mapping versions, while newly created non-CQL3 tables require type mapping version 1, and new tables, including those using compact storage, created using CQL 3 require type mapping version 2. CQL 3 is the default mode in Cassandra 2.x, which is based on CQL specification 3.1.0.

<dseTypeMappingVersion>2</dseTypeMappingVersion>

Set the value to 1 or 0 to enable one of the other versions. Switching between versions is not recommended after the Solr core has been created successfully: attempting to load a solrconfig.xml with a different dseTypeMappingVersion configuration and reloading the Solr core will cause an error.