-
Notifications
You must be signed in to change notification settings - Fork 15
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
Importing data from Elasticsearch #5
Comments
@saig0 first, i'd like to say that it's a great effort as there's currently no way to read Zeebe data easily. I would like to clarify this, when ES exporter is enabled, Operate uses ES transformers in order to create its own data, so data gets built on the fly when it is pushed by the exporter. Since the approach you chose is to create a local DB, I was wondering what would be the approach to support importing data from ES. |
@asaf, my idea is similar to Operate.
The difference to Operate is that the data is stored in a database that is maybe not ES. |
@saig0 ah, I thought operate puts some "processors" on ES somehow, yea fair enough, |
Hi there, |
@mohit2494 awesome 🎉 The basic idea here is to import the data from ES and store it similar to the Hazelcast importer.
The data in ES are generated by the ES exporter: https://github.com/zeebe-io/zeebe/tree/develop/exporters/elasticsearch-exporter Please ask if you've any question or need help :) |
Thank you so much for the reply. It looks interesting, though a bit challenging. Can I have an email id where I can get in touch. Best. |
@mohit2494 you can get in touch using the Zeebe Slack channel. You can ask questions in general or contact me directly. |
@saig0 is there any idea of an ETA for this at all? |
@fromz no ETA. Currently, I don't have any plans to work on it because I don't have a concrete need for it. But I'm open to contributions from the community. 🚀 |
The text was updated successfully, but these errors were encountered: