version_id in mview_state table not reset when *_cl table is recreated

[pascaladriaansen]

Preconditions

1. Magento 2.1.x, PHP 7.0.20
2. Production mode, crons enabled
3. All indexes are set to Update by Schedule

Steps to reproduce

1. In the admin, go to System > Index Management
2. Select any index, for example the 'Product Categories' index.
3. Select Update on Save from the dropdown at the top and click Save.
4. Select the same index again, select Update by Schedule from the dropdown and click Save.

Expected result

When executing step 4, the catalog_product_category_cl table is dropped and recreated, resetting its auto increment value to 0.
The version_id column in the mview_state table for the catalog_product_category index should be set to 0 so it matches the auto increment value of the catalog_product_category_cl table.

Actual result

The version_id column in the mview_state table for the catalog_product_category index is not set to 0.

It will only be set to 0 after manually running bin/magento index:reindex catalog_product_category on the command line.

This issue causes any logged change in the *_cl tables to be skipped until a manual reindex with bin/magento index:reindex catalog_product_category has been executed. Because of this, any changes made to the catalog related to the affected indexes will not become visible on the front end of your shop. I think this issue is highly related to #5836 (which hasn't seen any progress from Magento's side in a while). It is also somewhat related to #10203.

[pascaladriaansen]

Turns out this issue only occurs on our installations with the Mirasvit Search Spell-Correction module installed (part of their Sphinx Search Ultimate module). I'll inform them to fix this and close this issue.