Open avelanarius opened 3 years ago
/cc @jul-stas (I think you implemented printing of CDC options in cqlsh
, was there a important reason for printing those options in a separate line?)
@avelanarius IIRC the reason was to separate schema extensions from regular table options. In general, putting schema extensions among "normal" options, like AND schema_extension_X = abc
, can lead to an incorrect CREATE statement.
Maybe it's not the case with CDC schema extension so it can have special treatment while printing...
I think server side DESCRIBE should solve this one...
Small note: CDC options in server-side DESCRIBE were added only recently (5.2, 5.3 doesn't have it): https://github.com/scylladb/scylladb/commit/62ced6670231aa013acdfb2d1f4913a7b238e2db
@fruch - shall I move it to cqlsh repo?
@fruch - shall I move it to cqlsh repo?
You can move it
But it would need to be part of the scylla core as well, cause the server side describe
@fruch - shall I move it to cqlsh repo?
You can move it
But it would need to be part of the scylla core as well, cause the server side describe
I'll need to understand better what is needed in core - please open a separate issue if neede.
Currently,
cqlsh
prints CDC options inDESCRIBE TABLE
queries in a separate line:I think it would be better to print those options not in a separate line, but within the
CREATE TABLE
statement. That way it is more consistent with other options and easily copyable:(for a reference, Java Driver 3.x already prints it in that format when using
toString()
after this commit: https://github.com/scylladb/java-driver/commit/ae2254a2e6458fe99bb764af24d68df2590171d7)