You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by bbende <gi...@git.apache.org> on 2017/09/21 19:31:34 UTC

[GitHub] nifi-registry pull request #11: NIFIREG-22 Adding versionCount to VersionedF...

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi-registry/pull/11

    NIFIREG-22 Adding versionCount to VersionedFlow with back-end support…

    … for populating it

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bbende/nifi-registry NIFIREG-22

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-registry/pull/11.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #11
    
----
commit 07a757bc63c282ad4373f6b1ad160830fe8be64d
Author: Bryan Bende <bb...@apache.org>
Date:   2017-09-21T17:02:26Z

    NIFIREG-22 Adding versionCount to VersionedFlow with back-end support for populating it

----


---

[GitHub] nifi-registry pull request #11: NIFIREG-22 Adding versionCount to VersionedF...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/nifi-registry/pull/11


---

[GitHub] nifi-registry issue #11: NIFIREG-22 Adding versionCount to VersionedFlow wit...

Posted by bbende <gi...@git.apache.org>.
Github user bbende commented on the issue:

    https://github.com/apache/nifi-registry/pull/11
  
    Thanks @kevdoran , going to merge to master


---

[GitHub] nifi-registry issue #11: NIFIREG-22 Adding versionCount to VersionedFlow wit...

Posted by kevdoran <gi...@git.apache.org>.
Github user kevdoran commented on the issue:

    https://github.com/apache/nifi-registry/pull/11
  
    +1 @bbende - nice work on this!
    
    I reviewed code and did a full build with contrib-check. I ran the web api, verified creating/reading flow snapshots works, and new versionCount field returns correctly. The simplification of the backend through consolidating similar functionality is a nice improvement. LGTM
    



---