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
{{ message }}
This repository has been archived by the owner on Jul 6, 2023. It is now read-only.
Summary:
This is an attempt to define a generic API for execute admin operations on an OrientDB context.
Goals:
Add an API for run a range of not pre-defined admin operations, that can be executed from any connection type.
Non-Goals:
Define the operations that can be executed
Success metrics:
Stable API for admin operations that do not create issues on remote protocols
API that allow to evolve and add operations not yet defined
Motivation:
As today each admin operation needed to be defined in all the existing protocols, slowing down all the possible future evolutions, and adding a toll for every single enchantment to third party integrations.
Description:
As today all the structural operations have their own API, and some structural operations were moved inside the SQL (all distributed HA) but this operations can be run only inside a database context limiting the set of changes that can be done.
Here we propose to define a new API that can run SQL like operations on top of an OrientDB context, opening to the possibility to define a query language for any kind of structural operations inside OrientDB.
Risks and assumptions:
This move out the static typed API we had so far for structural operations, see for example the OrientDB#create that specify on the API what are the exact possible arguments, even though we can implements save APIs on top of this.
Impact matrix
Storage engine
SQL
Protocols
Indexes
Console
[ x ] Java API
Geospatial
Lucene
Security
Hooks
EE
Studio
The text was updated successfully, but these errors were encountered:
tglman
changed the title
[OEP 19] New API for execute pseudo sql command for admin operations
[OEP 21] New API for execute pseudo sql command for admin operations
May 24, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary:
This is an attempt to define a generic API for execute admin operations on an OrientDB context.
Goals:
Add an API for run a range of not pre-defined admin operations, that can be executed from any connection type.
Non-Goals:
Success metrics:
Motivation:
As today each admin operation needed to be defined in all the existing protocols, slowing down all the possible future evolutions, and adding a toll for every single enchantment to third party integrations.
Description:
As today all the structural operations have their own API, and some structural operations were moved inside the SQL (all distributed
HA
) but this operations can be run only inside a database context limiting the set of changes that can be done.Here we propose to define a new API that can run SQL like operations on top of an
OrientDB
context, opening to the possibility to define a query language for any kind of structural operations inside OrientDB.The proposed API are:
This API is borrowing the
OResultSet
from the database query API.One Important detail is the method name, please propose any other if this is not look good for you.
Alternatives:
Risks and assumptions:
This move out the static typed API we had so far for structural operations, see for example the
OrientDB#create
that specify on the API what are the exact possible arguments, even though we can implements save APIs on top of this.Impact matrix
The text was updated successfully, but these errors were encountered: