I'm not sure why this is happening at a glance but either way that Index should not be in the Liquibase changelog as the index is created by:

<addUniqueConstraint tableName="MinHash" columnNames="TopicID, MinHashFuncID"/>

Removed the incorrect create index statement in 1.4-SNAPSHOT build 201401151042

Note: The CHECKSUM for that create table will now be different, so you will need to run the following SQL before updating to the build above:

UPDATE `DATABASECHANGELOG` SET `MD5SUM` = '3:c21aeed0c7f7471ca63b39147e20c9b3' WHERE `ID` = '1' AND  `AUTHOR` = 'mcaspers' AND `FILENAME` = 'db/changelog/db.changelog-1.3.xml';

This version is now live on the test/development server.

I've reverted the above as I read the original part wrong and this didn't work as expected. 

I've now fixed it as per the initial specification in 1.4-SNAPSHOT build 201401151504. I've also made it so it'll be entirely managed by liquibase so no custom SQL needs to be executed, as well as added an index on the MinHash revision table since it was missing.

If you did run the above SQL, then here is the SQL to change it back:

UPDATE `DATABASECHANGELOG` SET `MD5SUM` = '3:c2e4c45c83480fa8b3c399e4c725e0d6' WHERE `ID` = '1' AND  `AUTHOR` = 'mcaspers' AND `FILENAME` = 'db/changelog/db.changelog-1.3.xml';

Note: This version is now live on the test/development server.

Downloaded a SQL backup from the prod server, deployed the REST server and confirmed that Liquidbase executed correctly and created the correct index.