This function is complete and can be used. The interfaces will be supported until the function is removed from the project via the deprecation process. There will be ongoing extensions to this function, but it will be done to ensure backward compatibility as far as possible. If there is a need to break backward compatibility, this will be discussed and reviewed in the community, with a documented timeline.
Data engine proxy services¶
The data engine proxy services support the behavior of the data engine proxy.
This server supports intercommunication from a Data Engine and the Data Engine OMAS.
A data engine is a technology that processes data to either copy it to a new location, transform it to a new format, so it can be consumed in a different way and/or derive new values from the data. The data engine may be retrieving data from multiple data sources and also writing to multiple data sources.
Information about the data that the data engine is consuming and creating, along with details of the processing it is doing is needed to provide lineage for the data sources. This is why it is important that we capture information about a data engine's processing in open metadata.
The Data Engine OMAS provides the API for capturing the processing of a data engine.
Where a Data Engine does not have direct support for publishing details of its processing to the Data Engine OMAS, a data engine proxy connector can be written for the Data Engine that uses the Data Engines native APIs and events to capture the required information and then translates it into calls to the Data Engine OMAS.
The data engine proxy connector runs inside a Data Engine Proxy Server on the OMAG Server Platform. The data engine proxy services are responsible for hosting the data engine proxy connector.