Replies: 1 comment
-
|
Great question! Using a common datastore (e.g. a Postgres table, which can be both a target and a source) is still the recommended way for now. We're ongoing a major redesign of CocoIndex. In the future, we'll likely support multi-stage flow, i.e. we can use some store as a target, and use the same store as the source, within the same flow. It'll enable more advanced use cases and make data transfer more efficient. If you're able to share more about your specific scenario and use cases, it'll also be very helpful for us. We'll make the future version better fit into users needs. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As of now each flow is separated and isolated. As of now the way for flows to have a common point of interaction could be a database , datastore , file system etc. Is there any programmatic way to discover multiple flows in cocoindex and pass args between them making them more flexible and elastic in nature
@georgeh0 , @badmonster0 requesting your thoughts on this !
Beta Was this translation helpful? Give feedback.
All reactions