scylla

Currently, there are no clear guidelines for determining when to log messages and what category to give them. We need to address the following, to begin with:

Distinguishing TRACE vs. DEBUG messages.
What events should be logged with INFO messages?
When actions fail:
- When to throw an exception and when to log.
- When to WARN vs. when to log an ERROR.

Flags

We need pretty much all the flags from https://github.com/volatiletech/sqlboiler#initial-generation, schema should be replaced with keyspace and models should be written to models/keyspace.

Output

For every table in a given keyspace generate Table metatata.

// TableName is generated metadata for <keyspace>.<table_name>.
struct TableName {
    Keyspace string
    Name

scylla

Here are 18 public repositories matching this topic...

scylladb / scylla

Document guidelines for determining log messages category

sstable file format is not documented

Users should not use SimpleStrategy for production (docs around AddDC are incorrect)

imWildCat / scylla

scylladb / gocqlx

Add a code generator that would extract tables and columns from a database

Flags

Output

yakirgb / puppet-scylladb

erathorus / spring-kotlin-reactive-scylla-example

r4fek / scylla-cli

rjeczalik / terraform-aws-scylla

rusher81572 / elasticsearch-scylla

yanniszark / go-nodetool

fed135 / scylla-driver

benniekrijger / todo-service-go

rjeczalik / terraform-aws-scylla-bench

akme / sonm-scylla

nepttune / scylla

rjeczalik / cqlenc

getnotified-me / cosmic-soup

Zinnion / cpp-driver

rjeczalik / packer-azure-scylla

Improve this page

Add this topic to your repo