Is your feature request related to a problem? Please describe.
KSqlDB added support for session variables on version 0.18 to make it easier to parameterise queries. More information about variables interpolation can be found here
Describe the solution you'd like
A potential solution would be to add an entry to the descriptor file to specify those variables as shown below:
Another alternative would be to specify these variables as a CLI argument (e.g. ksql-migrations tool follow this approach using a --define flag). Also, we can define session vars per each artefact, however, this could end up being too verbose and repetitive even though it could be mitigated with YAML references syntax.
Is your feature request related to a problem? Please describe. KSqlDB added support for session variables on version 0.18 to make it easier to parameterise queries. More information about variables interpolation can be found here
Describe the solution you'd like A potential solution would be to add an entry to the descriptor file to specify those variables as shown below:
Describe alternatives you've considered
Another alternative would be to specify these variables as a CLI argument (e.g. ksql-migrations tool follow this approach using a
--define
flag). Also, we can define session vars per each artefact, however, this could end up being too verbose and repetitive even though it could be mitigated with YAML references syntax.