This looks like a dupe of CASSANDRA-15086, which has been committed and will be included in 3.0.19.
> On Sep 11, 2019, at 5:10 PM, Cameron Zemek <came...@instaclustr.com> wrote: > > Have had multiple customer hit this CASSANDRA-15081 issue now, where > upgrading from older versions the sstables contain an unknown column (its > not present in the dropped_columns in the schema) > > This bug is serious as reads return incorrect results and if you run scrub > it will drop the row. So hoping to bring it some attention to have the > issue resolved. Note I have included a patch that I think does not cause > any regressions elsewhere. > > Regards, > Cameron --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
