[GitHub] bbende commented on issue #144: NIFIREG-209 Rebuild metadata DB from FlowPersistenceProvider when emp…

2019-01-28 Thread GitBox
bbende commented on issue #144: NIFIREG-209 Rebuild metadata DB from 
FlowPersistenceProvider when emp…
URL: https://github.com/apache/nifi-registry/pull/144#issuecomment-458262915
 
 
   Seems like a few people have tested this out and signed off, so I'm going to 
merge this to master.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] bbende commented on issue #144: NIFIREG-209 Rebuild metadata DB from FlowPersistenceProvider when emp…

2019-01-10 Thread GitBox
bbende commented on issue #144: NIFIREG-209 Rebuild metadata DB from 
FlowPersistenceProvider when emp…
URL: https://github.com/apache/nifi-registry/pull/144#issuecomment-453105411
 
 
   @MAliNaqvi the use-case for this feature wasn't really to keep two registry 
instances in-sync by using git in between. It was more for the case where 
someone lost their registry instance, but still had the git repo, for example 
maybe running registry in a container with an H2 DB and pushing to github, and 
then the container goes away, so all that remains is the github repo.
   
   As far as the diff'ing, the expectation is that diffs would be done through 
registry and not an external tool like github. There is already a REST 
end-point to compute the diff between two snapshots, but unfortunately the UI 
doesn't have anything yet to visualize this.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services