Support Questions

Find answers, ask questions, and share your expertise

How Come schema registry is not part of HDP?

avatar
Explorer

While installing Ambari we also installed mpack for HDF

now we want to create a cluster with HDP - HDFS / YARN / HBASE / KAFKA | HDF - NiFI / NiFi-registry / Schema-registry

to our surprise the NiFI / NiFi-registry do show in the HDP stack, but schema-registry is missing

when will this be fixed in the mpack, as it seems to be a missing entry in the mpack configuration

secondary question,

why will be able to use nifi 1.7 / nifi registry 0.2+

as we realy want to start using git integration?

1 ACCEPTED SOLUTION

avatar
Master Mentor
@Raymond Honderdors

-

The reason SAM and Schema Registry were removed when installing a HDP + HDF cluster has to do with dependency issues. It comes down to issues in Ambari 2.6.x version that come in to play when both HDP and HDF mpack are both installed that affects those services.
-
Those issues have been addressed in Ambari 2.7.0.

Since both HDP 3.0 and HDF 3.2 (not yet released) support Ambari 2.7.0, full support of SAM and Schema Registry will return with those versions loaded together.

-

HDF 3.2 is baselined off Apache NIFi 1.7 (so it will include everything in apache Nifi 1.7 plus some additional HDF specific changes and some additional fixes/enhancements)

-

Thank you,

Matt

-

If you found this Answer addressed your original question, please take a moment to login and click "Accept" below the answer.

View solution in original post

3 REPLIES 3

avatar
New Contributor

From the HDF 3.1.2 installation documentation:
[Important>Important You cannot install SAM and Schema Registry for HDF 3.1.x on an HDP 2.6.4 or 2.6.5 cluster, and you cannot upgrade these services from a previous HDP cluster.

avatar
Explorer

i did read this as well, i just wonder why this is as there is no real limitation, as far as i can see

avatar
Master Mentor
@Raymond Honderdors

-

The reason SAM and Schema Registry were removed when installing a HDP + HDF cluster has to do with dependency issues. It comes down to issues in Ambari 2.6.x version that come in to play when both HDP and HDF mpack are both installed that affects those services.
-
Those issues have been addressed in Ambari 2.7.0.

Since both HDP 3.0 and HDF 3.2 (not yet released) support Ambari 2.7.0, full support of SAM and Schema Registry will return with those versions loaded together.

-

HDF 3.2 is baselined off Apache NIFi 1.7 (so it will include everything in apache Nifi 1.7 plus some additional HDF specific changes and some additional fixes/enhancements)

-

Thank you,

Matt

-

If you found this Answer addressed your original question, please take a moment to login and click "Accept" below the answer.