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

Review CREATE STREAM and CREATE MATERIALIZED VIEW syntax #128

Open
4 tasks
jfallows opened this issue Oct 29, 2024 · 0 comments
Open
4 tasks

Review CREATE STREAM and CREATE MATERIALIZED VIEW syntax #128

jfallows opened this issue Oct 29, 2024 · 0 comments
Assignees
Labels
story Feature description from user's perspective

Comments

@jfallows
Copy link
Contributor

jfallows commented Oct 29, 2024

Describe the desired outcome from the user's perspective
As appdev, I want to create request-response APIs via zillabase simply in SQL.

Acceptance criteria

  • Map as closely as possible to existing concepts
  • Minimize introduction of zilla-specific complexity if possible

Additional context
Consider syntax such as CREATE ZSTREAM ... and CREATE ZSTREAM ... WITH ( reply_to= ... } etc.
Consider syntax such as CREATE ZTABLE ... to implicitly trigger source and sync to Kafka.
Consider syntax such as CREATE ZVIEW ... to implicitly trigger sync only to Kafka.

This implies SHOW ZSTREAMS, SHOW ZTABLES and SHOW ZVIEWS.

Consider syntax CREATE TABLE ... to pass through without implicitly triggering source and sync to Kafka.

Note: in each case with Z prefix, it represents an API we expose via Zillabase.

Tasks

  • Update schemas to catalog z related queries into a separate schema and make public schema as defaul
  • Support ZSTREAM, ZVIEW, and ZTABLE syntax
  • Enhance ZSTREAM to support reply_to
  • Support identity filtering in ZSTREAM, ZVIEW, and ZTABLE queries
@jfallows jfallows added the story Feature description from user's perspective label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story Feature description from user's perspective
Projects
None yet
Development

No branches or pull requests

2 participants