Make blackhole max index key length comparable to InnoDB #335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the maximum index key length for an InnoDB table is 3072 bytes.
We typically use the Blackhole storage engine on various replicas with low storage space, or other requirements.
The expectation is there that you should be able to run an ALTER TABLE ... ENGINE=BLACKHOLE; command without issues on any InnoDB table. However, if the index length is > 1000 bytes this fails.
This PR aligns the maximum key length with the InnoDB storage engine.