An unusual problem is happening with the DIH on a field that is an unsigned BIGINT in the MySQL database. This is Solr 4.9.1 without SolrCloud, running on OpenJDK 7u79.
During actual import, everything is fine. The problem comes when I restart Solr and the transaction logs are replayed. I get the following exception for every document replayed: WARN - 2015-05-19 18:52:44.461; org.apache.solr.update.UpdateLog$LogReplayer; REYPLAY_ERR: IOException reading log org.apache.solr.common.SolrException: ERROR: [doc=getty26025060] Error adding field 'file_size'='java.math.BigInteger:5934053' msg=For input string: "java.math.BigInteger:5934053" I believe I need one of two things to solve this problem: 1) A connection parameter for the MySQL JDBC driver that will force the use of java.lang.* objects and exclude the java.math.* classes. 2) Write the actual imported value into the transaction log rather than include the class name in the string representation. Testing shows that the toString() method on BigInteger does *NOT* include the class name, so I am confused about why the class name is being recorded in the transaction log. For the first solution, I've been looking for a MySQL connection parameter to change the Java object types that get used, but so far I haven't found one. For the second, I should probably open an issue in Jira, but I wanted to run it by everyone before taking that step. I have another index (building from a different database) where this isn't happening, because the MySQL column is *NOT* unsigned, which causes the JDBC driver to use java.lang.Long instead of java.math.BigInteger. Thanks, Shawn