Closed akhilreddyjirra closed 5 years ago
will let @cmgrote handle this. He has a tougher challenge with combining egeria code and atlas code together. May be worth considering whether any combined build (docker or other) should be an additional required check --
From the build steps, this looks like this is the Atlas fork (eg. ..../docker/atlas
rather than ..../docker/apache-atlas
)? This is a fork that we don't plan to maintain going forward -- I understood that it was still working, but now may be broken (?)
Oops - I misread the name. I'll check
From the build steps, this looks like this is the Atlas fork (eg.
..../docker/atlas
rather than..../docker/apache-atlas
)? This is a fork that we don't plan to maintain going forward -- I understood that it was still working, but now may be broken (?)
@cmgrote i am assuming ../docker/atlas
is not required instead apache-atlas will consider.
The failing constants are defined in org.odpi.openmetadata.accessservices.dataplatform.utils - refactoring likely means atlas isn't pulling in all the needed dependencies
However as @cmgrote mentioned this atlas fork will be removed just as soon as we get some replacement UIs in place so we won't put too much effort into fixing.
I'll take a short look at the egeria dependencies used by the fork
Actually the first failure relates to getActiveTypesByWildCardName. This was removed in e1d1eb94c3974d75fe312f58c1f4dc667c043634 which was committed on June 30
It would be possible to refactor the connector, but I think we're fighting a losing battle as we want to move the egeria code on
@cmgrote @mandy-chessell @grahamwallis I think it's time to retire the old atlas connector
We could see if old atlas image will still work with the help charts but given @cmgrote 's work to build the new connector is progressing, and a merge on our container stuff is blocked whilst we supported old atlas, I'm inclined to say let's take it and move on.
It will impact consumers wanting to view what is in Egeria, we can individually talk to them and suggest using postman in the interim, with initial versions of new UIs expected in weeks
Ok?
If so I'll do the removal and merge
I've now removed the atlas fork in #1236 and merged
We now need to remove the build for the atlas fork
I shall raise a helpdesk item for this (as a request to your team?)
issue was raised. closing here
when I ran mvn clean install -Ddocker -Ddocker.repo=XXX for docker atlas. Giving me the below error.