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

Have you ever thought of integrating OrientDB as a node level store for Apache Spark? #10170

Open
MironAtHome opened this issue Feb 28, 2024 · 1 comment

Comments

@MironAtHome
Copy link

I have pulled this project out of a thin air and thought that columnar datastore can be one upped by graph data store, and on top of it with indexes ( distributed ).
The cool part is it's just an optimizer plug in to have it to generate accessors for OrientDB instead of parquet.
I think we can push GPU's out the window, for majority of the projects and finally do most of computations in memory.
And I don't mean going delta architecture. Since JVM can use all the memory on the node ( and OrientDB is thread friendly, so, it can safely multi-task ).

@MironAtHome MironAtHome changed the title Have you ever thought of integrating OrientDB as a node for Apache Spark? Have you ever thought of integrating OrientDB as a node level store for Apache Spark? Feb 28, 2024
@tglman
Copy link
Member

tglman commented Feb 28, 2024

Hi,

This is probably possible, and quite interesting, on the other end is quite out of the scope of the OrientDB project itself, in the meaning that we would happily help someone else to implement it, but not do it ourselves.

Regards

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

No branches or pull requests

2 participants