exportAsString improvements (sort, format, clustering order)
Description
While evaluating I found some other inconsistencies with exportAsString
user types, tables, views, functions and aggregates are not consistently ordered (use ConcurrentHashMap which has no ordering guarantees)
Materialized views are not formatted in exportAsString on {{TableMetadata}]
Spacing on formatted materialized views is off.
Clustering order is not included if all clustering is ascending, this is inconsistent with python driver export_as_string so felt that would be good to include it.
Columns are not quoted if necessary in clustering order
Additional Newline missing after index/materialized view and next table/keyspace.
When printing table options formatted, "AND" was prefixed by 3 spaces instead of 4 (like columns are offset).
While evaluating I found some other inconsistencies with
exportAsStringuser types, tables, views, functions and aggregates are not consistently ordered (use
ConcurrentHashMapwhich has no ordering guarantees)Materialized views are not formatted in
exportAsStringon {{TableMetadata}]Spacing on formatted materialized views is off.
Clustering order is not included if all clustering is ascending, this is inconsistent with python driver
export_as_stringso felt that would be good to include it.Columns are not quoted if necessary in clustering order
Additional Newline missing after index/materialized view and next table/keyspace.
When printing table options formatted, "AND" was prefixed by 3 spaces instead of 4 (like columns are offset).
Slight spacing issues in UDFs and UDAs
Return type for UDF should never be frozen