-
Notifications
You must be signed in to change notification settings - Fork 14
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
projections API #22
Comments
looks like the eventstore team threw up some docs on the grpc projections API https://developers.eventstore.com/clients/grpc/projections/ just yesterday 🚀 |
Hi there, have you been able to look at the new documentation and understand projections better yet? (untold underlying question: any idea how complex and time consuming implementing them would be?) |
I haven't looked into it myself. We drive projections through the HTTP API since the HTTP API is easier to integrate with infrastructure-as-code tools (terraform, ansible, etc.), so we don't have a good use-case for using projections via Elixir. With the addition of subscriptions/reads of the I would prefer that the projections API code is added by someone with a use-case for it. It should be somewhat easy: Spear just needs a nice wrapper for the projection RPCs in
#49 could be used as a good example. The gRPC code already exists (https://github.com/NFIBrokerage/spear/blob/main/lib/spear/records/projections.ex) so you could use projections now with a combination of |
I didn't know that Thank you for taking the time to answer ✨ |
connects #7
the projections API is a bit cryptic for me
I've been able to hobble my way through the rest of the protos pretty much just on sheer experimentation and checking with the other client libraries. The projections API is a bit out there and I'm not really sure what the difference is between a continuous, a transient, and a one-time projection (just to begin with). The Event Store team is supposedly in a major documentation refactor, so I'm gonna put this one on hold and go get the more familiar persistent subscriptions API.
The text was updated successfully, but these errors were encountered: