Broken pipe when killing a client about scylladb HOT 5 CLOSED

This is the schema for it (to load using cqlsh):
CREATE KEYSPACE examples
WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 1};

USE examples;

CREATE TABLE songs (
id uuid PRIMARY KEY,
title text,
album text,
artist text,
tags set,
data blob
);

from scylladb.

client side:
cqlsh> CREATE KEYSPACE examples
... WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 1};
cqlsh>
cqlsh> USE examples;
cqlsh:examples>
cqlsh:examples> CREATE TABLE songs (
... id uuid PRIMARY KEY,
... title text,
... album text,
... artist text,
... tags set,
... data blob
... );
SyntaxException: <ErrorMessage code=2000 [Syntax error in CQL query] message="Failed parsing statement: [CREATE TABLE songs (
id uuid PRIMARY KEY,
title text,
album text,
artist text,
tags set,
data blob
);] reason: : syntax error...
">

Server side:
...
Seastar HTTP server listening on 127.1.11.1:10000 ...
WARNING: Not implemented: AUTH
warning: ignoring event registration
WARNING: Not implemented: METRICS
WARNING: Not implemented: PERMISSIONS
WARNING: Not implemented: PAGING
[shard 0] query_processor - The statement: CREATE TABLE songs (
id uuid PRIMARY KEY,
title text,
album text,
artist text,
tags set,
data blob
); could not be parsed: : syntax error...

from scylladb.

In CREATE TABLE statement in 'tags' column definition 'set' should have an elements' type definition, e.g. set.

from scylladb.

The exact cut&paste string is here: https://github.com/cloudius-systems/urchin/wiki/Using-example-perf.c-from-the-cpp-driver

from scylladb.

The exceptional future that had been ignored was the one stored in _ready_to_respond. The solution is to return it from transport::cql_server::connection::process().
The appropriate patch has been committed to the master: commit 86e28bb

from scylladb.