Currently there is no easy way to over come this case because deletes and
its tracking takes precedence before the filter is even applied.
I get your case where you really don't know the columns which could have
been previously deleted and hence you specify the entire range of
columns in the filter. When this Put/Delete combination keeps increasing
then you end up in these issues.
Am not aware of the use case here, but is there any better way to handle
your schema for these cases?
On Mon, Sep 16, 2019 at 10:54 PM Solvannan R M <[EMAIL PROTECTED]lid>