Skip to content
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

Unify the query execution logic across all modes (interactive, headless) #1544

Closed
ybyzek opened this issue Jul 6, 2018 · 3 comments

Comments

@ybyzek
Copy link
Contributor

commented Jul 6, 2018

Unify the query execution logic across interactive mode, non interactive mode, and RUN SCRIPT.

This issue is desirable as it relates to:
#1031
#1320

@miguno miguno changed the title Unify the query execution logic across all modes Unify the query execution logic across all modes (interactive, headless) Oct 2, 2018

@miguno miguno added the enhancement label Oct 2, 2018

@apurvam

This comment has been minimized.

Copy link
Contributor

commented Nov 9, 2018

@big-andy-coates assigning this to you since you are already looking into this problem. It would be good to unify the behavior of multiline statements across modes as well. Right now, I think they are supported in the CLI, but what about in run script and in non-interactive mode?

@miguno

This comment has been minimized.

Copy link
Member

commented Nov 12, 2018

Also, @hjafarpour recently completed Sync Application(headless) mode behavior with the interactive mode. #1599. Has that PR improved the situation described in this ticket? For example, that PR fixed #1320, which @ybyzek referred to in her original message at the very top here.

Lastly, there is the related ticket Avro limitation for commands in run script versus interactive #1031 -- similar to @apurvam's comment above about RUN SCRIPT.

@big-andy-coates

This comment has been minimized.

Copy link
Member

commented Mar 8, 2019

This is done now. The only piece of the puzzle left to do is proper support for schema inference in headless mode, i.e. storing the KSQL schema somewhere so things do not get messed up if schemas evolve in the schema registry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.