Enforce chunk size in cassandra data output stream

Signed-off-by: Paul Bui-Quang paul.buiquang@rte-france.com

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

[x] The commit message follows our guidelines

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) bug fix

What is the current behavior? (You can also link to an open issue here) Also (not fixed in this PR), the chunk size is not enforced if the write buffer length used with this outputstream is greater than the chunk size. For instance:

String nodeId = "someId";
String dataNodeName = "somedataname";
byte[] data = new byte[N]; // where N is greater than chunk size
Arrays.fill(data, (byte)0);
try(BinaryDataOutputStream os = new BinaryDataOutputStream(nodeId, dataNodeName))  {
  os.write(data); // will call os.write(data, 0, data.length)
}

will result in one only chunk written to database instead of the proper chunk count expected. Usually the OutputStream is wrapped in an other one that buffers the data way under the size of the configured chunk size, but this is no guarantee.

What is the new behavior (if this is a feature change)? The data is splitted accordingly.

powsybl / powsybl-afs

Enforce chunk size in cassandra data output stream #56