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

Explore supporting StreamExecute/OLAP workloads #55

Open
mattrobenolt opened this issue Aug 23, 2022 · 1 comment
Open

Explore supporting StreamExecute/OLAP workloads #55

mattrobenolt opened this issue Aug 23, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@mattrobenolt
Copy link
Member

mattrobenolt commented Aug 23, 2022

Within some contexts, especially serverless, the memory limits are very low in process. So it can be desirable when performing aggregations in process, or if also streaming out to the end user, to be able to leverage StreamExecute from our API.

I will say, this is going to be rather non-trivial, but I'd like us to see what it'd take to support without fully adopting connect-web or protobufs.

Streaming requires adopting the Connect protocol, rather than simply application/json, which can be done, and is done within connect-web. https://connect.build/docs/protocol#streaming-response

To add to this, this feature is required to support OLAP queries.

cc @reconbot

@mattrobenolt mattrobenolt added the enhancement New feature or request label Aug 23, 2022
@mattrobenolt
Copy link
Member Author

This is a functioning POC https://gist.github.com/mattrobenolt/6ca8c37185578cac8970de5a82dcfd52

It definitely needs more work. I also talked with the buf folks, and they agree that we should vendor in their codec stuff like I'm doing here.

@mattrobenolt mattrobenolt changed the title Explore supporting StreamExecute Explore supporting StreamExecute/OLAP workloads Oct 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant