I don’t have a good answer for you - I don’t know if scrub will fix this (you could copy an sstable offline and try it locally in ccm) - you may need to delete and reinsert, though I’m really interested in knowing how this happened if you weren’t ever exposed to #14008.
Can you open a JIRA? If your sstables aren’t especially sensitive, uploading them would be swell. Otherwise , an anonymized JSON dump may be good enough for whichever developer looks at fixing this -- Jeff Jirsa > On May 15, 2019, at 7:27 PM, Ahmed Eljami <ahmed.elj...@gmail.com> wrote: > > Jeff, In this case is there any solution to resolve that directly in the > sstable (compact, scrub...) or we have to apply a batch on the client level > (delete a partition and re write it)? > > Thank you for your reply. > >> Le mer. 15 mai 2019 à 18:09, Ahmed Eljami <ahmed.elj...@gmail.com> a écrit : >> effectively, this was written in 2.1.14 and we upgrade to 3.11.3 so we >> should not be impacted by this issue ?! >> thanks >>
