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
Move common functions in DDC engines to a higher level abstraction like a common engine.
Refactor runtimeInfo that make this concept more clear to developers, when to use runtimeInfo, what property should be put into runtimeInfo? Another confused concept would be base.RuntimeInterface, try to discriminate these two concepts.
BTW, is it possible to make integration with a new runtime's much easier with less coding? For example, runtime developers can forget about the lifecycles and simply implement the following components/functions:
transform function and a runtime helm package: This is the core that Fluid sets up a runtime in the cluster.
Functions that may interact with the runtime: For example, mounting/umounting functions, cache status report, health check.
[Optional] Data operations like DataLoad, DataMigrate and DataProcess
The text was updated successfully, but these errors were encountered:
common
engine.base.RuntimeInterface
, try to discriminate these two concepts.BTW, is it possible to make integration with a new runtime's much easier with less coding? For example, runtime developers can forget about the lifecycles and simply implement the following components/functions:
transform
function and a runtime helm package: This is the core that Fluid sets up a runtime in the cluster.The text was updated successfully, but these errors were encountered: