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

api for a kappa-view #1

Open
dominictarr opened this issue Jun 26, 2019 · 1 comment
Open

api for a kappa-view #1

dominictarr opened this issue Jun 26, 2019 · 1 comment

Comments

@dominictarr
Copy link

I'm trying to understand how I might create an adapter that allows flumeviews and kappaviews to be interchangeable.

in flume, views expose a createSink method, and a since observable.

in kappa, it looks like the batch method is used, which takes a callback, but doesn't expose where it's up to exactly. Or does it in a way I havn't figured out yet?

I also noticed that multifeed-index accepts ops that have both keys and sequences - it indexes many logs not just one log. It seems like this might ruin my plan to make an adapter, because flume assumes a single log (which in ssb is many logs combined, in receive order). I guess it would be easy to adapt a kappa view to flume, because if the view can support many logs, then it can support just one.

@hackergrrl
Copy link
Member

You're right: it doesn't expose indexing progress right now, at least not directly. However, you could deserialize the opaque state object given to the storeState userland callback to figure it out if you really needed to.

Yeah, this is a tricky problem, since flumedb hands off the multiple feeds problem to ssb, but they're first-class in kappa..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants