KSQL should warn when forcing CSAS object names to upper case

[rmoff]

Creating a stream called mysql_customers, KSQL instead calls it (and the underlying topic) MYSQL_CUSTOMERS.

Either KSQL is case-sensitive or it isn't. If it is, then it should warn the user (probably in the output from the CSAS) that it's used a different object name from that specified in the DDL

ksql> CREATE STREAM mysql_customers AS SELECT * FROM CUSTOMERS_SRC PARTITION BY ID;

 Message
----------------------------
 Stream created and running
----------------------------

ksql> CREATE TABLE CUSTOMERS WITH (KAFKA_TOPIC='mysql_customers', VALUE_FORMAT ='AVRO', KEY='ID');
 Could not fetch the AVRO schema from schema registry. Subject not found.; error code: 40401

ksql> show streams;

 Stream Name         | Kafka Topic           | Format
------------------------------------------------------
 CUSTOMERS_SRC_REKEY | CUSTOMERS_SRC_REKEY   | AVRO
 RATINGS             | ratings               | AVRO
 CUSTOMERS_SRC       | asgard.demo.customers | AVRO
 MYSQL_CUSTOMERS     | MYSQL_CUSTOMERS       | AVRO
------------------------------------------------------

Bonus points : From a UX point of view, it would be nice if KSQL can't find a schema that it did a second check against the Schema Registry and told the user that there is a schema of that name and did they mean to use that one instead?

[big-andy-coates]

Maybe we could include the stream name in the message returned? e.g.

ksql> CREATE STREAM mysql_customers AS SELECT * FROM CUSTOMERS_SRC PARTITION BY ID;

 Message
----------------------------------------------------
 Stream 'MYSQL_CUSTOMERS' created and running
----------------------------------------------------