The only document I could find about scylla bootstrapping process was this:
Directory layout and bootstrapping
So users, customers, field teams and engineers have to rely on either reading the code or recurring to C*/DS documentation (which is not entirely applicable, I guess).

Can someone familiar with scylla boot

Is your feature request related to a problem? Please describe.
Provide help in CLI for sub-commands

Describe the solution you'd like
Sub-commands help should describe the sub-command's functionality and options available for the sub-command

Describe alternatives you've considered
N/A

Additional context
See: golang-migrate/migrate#370

The docs have a great intro that explains the technology buildup to arrive at inventing stream but then it stops without explaining how stream uses Cassandra + Redis (plus celery message queue?) to solve this problem. (For all I know it doesn't.)

As a developer, a quick explanation of how this framework solves the

  File "/root/miniconda3/bin/pipeline", line 11, in <module>
    sys.exit(_main())
  File "/root/miniconda3/lib/python3.7/site-packages/cli_pipeline/cli_pipeline.py", line 5734, in _main
    _fire.Fire()
  File "/root/miniconda3/lib/python3.7/site-packages/fire/core.py", line 127, in Fire
    component_trace = _Fire(component, args, context, name)
  Fil

The doc on https://docs.janusgraph.org/basics/schema/#automatic-schema-maker says automatically created property key has data type Object.class

By default, implicitly created edge labels have multiplicity MULTI and implicitly created property keys have cardinality SINGLE and data type Object.class.

However, my testing shows that Default Schema Maker automatically infers the type of propert

This reference to golang documentation is completely wrong:
https://github.com/gocql/gocql/blob/e6d89e6c5ab3faf5127fc95fb85477f39ac9c792/conn.go#L764-L766

Original documentation says:

WriteTo writes data to w until there's no more data to write or when an error occurs. The return value n is the number of bytes written. Any error encountered during the write is also returned.

https://gola

This pattern works and allows you to use run-time specified schemas, so I think it should be documented:

def myQuery[T:SchemaMeta] = quote { query[T] }
case class Person(id:Int, name:String)
run(myQuery[Person])
// SELECT x.id, x.name FROM Person x

(If we choose to some-day support Java-beans, it may also be useful for that)

@getquill/maintainers

I'm not certain this is a bug in the code, but I feel like I've been mislead with the documentation and the behavior doesn't match what I thought I'd expect. I am using v1.22.0

First off, my use-case I think is a bit non-standard so that could be part of the problem. I have a consistent schema (Tables/Databases) that exist in multiple keyspaces (of which I don't know ahead of time, and aren't sta

https://github.com/spotify/ffwd-client-java/tree/master#opencensus-exporter

that way we can see bigtable metrics.

When setting the monitor.tail property, it's possible to tail/update only filenames, and not directories:

https://github.com/Landoop/stream-reactor/blob/master/kafka-connect-ftp/src/main/scala/com/datamountaineer/streamreactor/connect/ftp/source/FtpFileLister.scala#L41

So, when a support for a recursive structure is required, it can be done in a way like this:
`connect.ftp.monitor.tail=/**:

trait CassandraAsyncContext{
  trait Quoted[T]{
    def query: String
  }
}
trait Context {
  val context: CassandraAsyncContext
}

@free trait CassandraAlgebra extends Context {
  def runSingle[T(q: context.Quoted[T]): FS[List[T]]
}

after macro generation, trait Context got removed.

Java source code:
https://github.com/datastax/java-driver/tree/4.x/examples/src/main/java/com/datastax/oss/driver/examples/mapper

Requirements:

• It should be placed in examples/killrvideo dir
• Each java package should come as a file - it should be a flat package
• It should be simple, easy to understand so that others can copy ideas from it
• It should use migrate to create schema
• It

@chrisbennight missed a badge!

Hi,

I just had a suggestion around documentation around the CLI, specifically with regards to passing a response file.

If possible, under the Examples subheading could we label the contents of the args.txt file to make it explicit.

Just adding a simple "Contents of args.txt:" I feel would be helpful.

Thanks

Spotted on 1.4.1 (9853df3)
Reaper showing replay option for "Done" segment. Why would this be needed? if repair is Done successfully.

We use the connect ui in a Kubernetes setup where a sidecar of the connect-ui is notified when a new connect cluster joins. This sidecar updates then the caddy server configuration (mostly proxy settings).

Unfortunately, the caddy server does not restart automatically in case of config changes.

Proposal: use a tool like inotifywait that listens on changes of the caddy config and restart th

Looks like there is an issue with source links in https://doc.akka.io/api/akka-persistence-cassandra/0.103/akka/persistence/cassandra/ -- clicking on package.scala I get a 404: https://github.com/akka/akka-persistence-cassandra-1.x/tree/v0.103/core/src/main/scala/akka/persistence/cassandra/package.scala#L1.

Note the -1.x in the URL -- I guess it's from https://github.com/akka/akka-persist