Dmitry Kropachev comments

Results 289 comments of


                                            Dmitry Kropachev

SCT raised a CoreDumpEvent, but the coredump itself was not found anywhere

What we can do is to stream cores to s3 via curl and pick them up form there

<wip> update ci dependencies

@Oneill38 , it failed with: ``` go: errors parsing go.mod: /home/runner/work/gocql/gocql/go.mod:16: unknown block type: retract Error: Process completed with exit code 1. ```

Create schema with autoresize rf for multidc cluster with tablets enabled and configured with on dc with single zero token node failed and terminate the c-s

> > Assigning to the drivers team for now. > > [@dkropachev](https://github.com/dkropachev) could you confirm that you agree with Karol's assignment to your team? I prefer to validate as this...

Create schema with autoresize rf for multidc cluster with tablets enabled and configured with on dc with single zero token node failed and terminate the c-s

@aleksbykov , @fruch , we are tring to indetify scope of it, could you please point me to what makes `replication factor` to be `auto-resize` in this test ?

Create schema with autoresize rf for multidc cluster with tablets enabled and configured with on dc with single zero token node failed and terminate the c-s

@Bouncheck , can you please take a look at it from the perspective of https://github.com/scylladb/java-driver/issues/317.

Create schema with autoresize rf for multidc cluster with tablets enabled and configured with on dc with single zero token node failed and terminate the c-s

> [@bhalevy](https://github.com/bhalevy) > > To be precise I think there are two issues. > > * CREATE with rf=3 succeeded, and allocated 3 replicas to DC3. But DC3 does not...

Create schema with autoresize rf for multidc cluster with tablets enabled and configured with on dc with single zero token node failed and terminate the c-s

Please retest with new c-s, it should be fixed there.

Caching prepared statements automatically

> https://github.com/scylladb/scylla-go-driver supports transparently preparing and caching prepared statements. As of my understanding, python driver does not support this and if we would, it should be implemented in this repo....

Select with IN clause

> I looked more closely into [table.go](https://github.com/scylladb/gocqlx/blob/master/table/table.go) and it seems as an intended behavior to always add `WHERE` clause with partition key (it is expected in tests). I would advise...