keith-turner commented on PR #5371:
URL: https://github.com/apache/accumulo/pull/5371#issuecomment-2691737340
The added javadoc is intentionally vague about what table splits are removed
because its really hard to describe. Looked at the code and wrote the
following test program when trying to figure this out.
```
@Test
public void testDR() throws Exception {
String[] tables = getUniqueNames(3);
try (AccumuloClient client =
Accumulo.newClient().from(getClientProps()).build()) {
SortedSet<Text> splits = new TreeSet<>();
splits.add(new Text("b"));
splits.add(new Text("f"));
for(var start : List.of("a","b","c")){
for(var end : List.of("e","f","g")){
client.tableOperations().create(tables[0]);
client.tableOperations().addSplits(tables[0], splits);
client.tableOperations().deleteRows(tables[0], new Text(start),
new Text(end));
System.out.printf("start:%s end:%s splits:%s\n", start, end,
client.tableOperations().listSplits(tables[0]));
client.tableOperations().delete(tables[0]);
}
}
}
}
```
this program prints.
```
start:a end:e splits:[f]
start:a end:f splits:[b]
start:a end:g splits:[b]
start:b end:e splits:[b, f]
start:b end:f splits:[b]
start:b end:g splits:[b]
start:c end:e splits:[b, f]
start:c end:f splits:[b, f]
start:c end:g splits:[b]
```
The way splits are removed depends not on how the split itself overlaps with
the delete range, but rather how the tablet
that the split is a part of overlaps with the delete range.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
