Details
-
Improvement
-
Status: Open
-
Low
-
Resolution: Unresolved
-
None
Description
These classes have been a bit of a mess for a while, with very poor isolation of concerns and lack of consistent approach. We've done a lot of tidying of behaviour, so I think we're now in a good place to restructure them to more clearly represent that behaviour in the simplest way possible.
In my opinion these should all coexist in a single package, since they are so tightly related. The details should not leak outside of this package as far as possible, so there is no leakage into e.g. SSTableWriter.
At the same time we should, as suggested by Blake, separate SequentialWriter from its Transactional behaviour.
Attachments
Issue Links
- relates to
-
CASSANDRA-10158 Rationalize implementations of DataInputPlus and DataOutputPlus
- Open