milleruntime commented on issue #2076:
URL: https://github.com/apache/accumulo/issues/2076#issuecomment-839708372
If I gave each enum in `LogEvents` a unique number for sorting, then I
wouldn't have to store the string in the column family. The new numbering could
look like this:
<pre>
// OPEN = 0
// DEFINE_TABLET = 1
// COMPACTION_START = 2
// COMPACTION_FINISH = 3
// MUTATION = 4
// MANY_MUTATIONS = 5
</pre>
It would be extra convenient if the `ordinal()` of the enum corresponded to
these numbers but currently that is not the case. The sorted WALs between
previous versions and this one will already be incompatible so it may not be a
big deal to change the order of the `LogEvents` enum. But I wonder if it could
lead to some crazy bugs if a user were to recover an old WAL.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
