You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ).
The text was updated successfully, but these errors were encountered:
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
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.
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 ).
The text was updated successfully, but these errors were encountered: