Dmitry Kropachev

@fruch , plan is to merge last pending PR: https://github.com/scylladb/python-driver/pull/397, rebase this PR and see what is left, which should be only pipeline changes.

@fruch , @Lorak-mmk after all rebases it is left only with python-related changes please take a look.

> @roydahan, @vponomaryov - @dkropachev is already working on fixing the problem with the nemesis. You can monitor the progress in #7029. This PR should be closed. Let's merge https://github.com/scylladb/scylla-cluster-tests/pull/7029...

# Column-based blobs compression ## General idea If client stores big blobs of data compressing data that goes into that field will reduce operations select/update footprint on both network and...

@mykaul , @Lorak-mmk , let's move discussion here

@mykaul, this is continueation of [comment](https://github.com/scylladb/gocql/pull/221#issuecomment-2242848697) > > If client stores big blobs of data compressing data that goes into that field will reduce operations select/update footprint on both network...

> I think we are talking about different things. Did you see the PR implementing this feature? #221 It is a draft to quickly test feature out and no good...

> > > It uses a prefix (by default `lz4:`) to tell if the value fetched from DB is compressed or not. It also has a limit, so it only...

> > https://opensource.docs.scylladb.com/stable/troubleshooting/large-rows-large-cells-tables.html > > Thanks! > > > You are right. I missed that part. When we proposed this feature I assumed that you don't need to prepend the...

> Right, Not DoS, but incorrect data would be returned, because code would treat this as raw uncompressed data. It's probably worse :/ If you forge prefix and header properly...