-
Notifications
You must be signed in to change notification settings - Fork 260
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
Remove Data Platform OMAS #5319
Comments
Data Platform OMAS? |
As far as I know Data Engine OMAS is still used extensively for lineage (?) |
Duly noted @planetf1. I will consider this and have step to remove Data Platform OMAS as part of the cassandra metadata extractor removal activity. I will create new issue to track this and link it here. Lets update the title on this though to say "Remove Data Platfom OMAS". |
@mandy-chessell @cmgrote @lpalashevski Yes 'data platform'. Apologies. So many overlapping terms causing mental capacity overflow |
@mandy-chessell I need confirmation, removing Data Platform OMAS also implies removing the dedicated governance server (data-platform-services) including admin-services and documentation parts, right? |
@lpalashevski yes :) - except leave the following file ... |
This is now addressed in #5344 Some occurences of Data Platform services in admin modules are not removed to preserve backward compatibility i.e. checks in server type classifier that I think are still needed (that pulls in configuration document and related classes...) We can disscuss it on the community call 10/06/2021 and decide if we completely remove the support. |
this has now been completed |
In #5314 some atlas/ranger etc related code was removed and it was noted that Data Engine OMAS can now be removed, since it's capabilities have been replaced by Integration Services
However currently the cassandra metadata extractor depends on Data Engine, so it seems prudent to remove the cassandra metadata extractor first (cc: @lpalashevski )and then return to complete the removal of data engine omas
The text was updated successfully, but these errors were encountered: