-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(ksql-connect): introduce syntax for CREATE CONNECTOR (syntax only) #3139
Conversation
@@ -291,6 +292,7 @@ qualifiedName | |||
identifier | |||
: IDENTIFIER #unquotedIdentifier | |||
| QUOTED_IDENTIFIER #quotedIdentifierAlternative | |||
| STRING #stringIdentifier |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ANSI standard is to have "
for identifiers and '
for constants - most DBs don't really follow this (Postgres does, but MySQL and SQL-Server don't). Since we use identifier
in tableProperties
it's either we allow '
or we deal with needing to do "foo"='bar'
which I think is incredibly confusing, or we duplicate a bunch of code to allow '
in table properties, but not in other identifiers...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need to add STRING
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of the other syntax only allow for "
for identifiers, not '
- I just reused STRING
because it allows for '
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Talked offline here. The problem is that identifiers and literals need to be differentiated in the select statements (e.g. SELECT 'foo'
and SELECT "foo"
are different, one refers to literals the other refers to a column)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Description
As part 2 of a series of PRs related to connect integration, this one adds syntax for
CREATE (SOURCE | SINK) CONNECTOR
. This does not wire in anything, these statements will parse but nothing more.Testing done
Unit testing
Reviewer checklist