Thanks,but this api is used to delete the entity,I'm afraid it can't be used to delete a deleted Relationship hardly. ... View more

You can try this using the Rest api:   # DELETE the Client curl -k -u admin:admin -H "X-Requested-By: ambari" -X DELETE "$HTTP_PROTOCOL://$CONSOLE_NODE:$PORT/api/v1/clusters/$CLUSTER/host_components?HostRoles/component_name.in(HDFS_CLIENT)&HostRoles/host_name.in(hostname01,hostname02)" # INSTAL the Client curl -v -k -i -u 'admin:admin' -H 'X-Requested-By: ambari' -X POST -d ' { "RequestInfo":{ "query":"Hosts/host_name.in(hostname01)" }, "Body":{ "host_components":[ { "HostRoles":{ "component_name":"HDFS_CLIENT" } } ] } }' '$HTTP_PROTOCOL://$CONSOLE_NODE:$PORT/api/v1/clusters/$CLUSTER/hosts'   ... View more

I know.Need FQDN likes testhost.magg.com,Thanks   ... View more

Thanks.I open the https for nifi.And it works when Knox and Nifi on same server.But when I deploy NIFI and KNOX separately, I am redirected infinitely when SSO logs in to NIFI and I find Cookies have problems. Is this because of cross-domain? Knox gateway.log has "JWT cookie successfully added." but nifi-user.log have " [<anonymous>] GET https://XXX:9443/nifi-api/flow/current-user"   ... View more

When I tried to turn on KnoxSSO for NIFI without https,I can access NIFI's Web UI through Knox,but I can also access the NIFI directly through port 10111 which no jump to Knox. So I tried to enable HTTPS while using Knox, and I got this error "Apache Knox SSO support cannot be enabled if the Login Identity Provider or OpenId Connect or SAML is configured."     ... View more