[ 
https://issues.apache.org/jira/browse/NIFIREG-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171776#comment-16171776
 ] 

ASF GitHub Bot commented on NIFIREG-18:
---------------------------------------

GitHub user bbende opened a pull request:

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

    NIFIREG-18 Refactor MetadataProvider to use an embedded database

    - Initial plumbing for H2 database
    - Setup Flyway with initial migration to define tables
    - Setup entity classes with repositories
    - Setup unit testing for repositories
    - Removed existing MetadataProvider concept
    - Removed provider impl module and moved remaining pieces into framework
    - Added MetadataService with DatabaseMetadataService implementation
    - Refactored RegistryService to use MetadataService
    - Introduced verbose flag on some end-points to control loading nested 
objects
    - Added ability to pass down paging/sorting params
    - Added endpoints for available fields
    - Adding ItemResource and ability to retrieve all items, or items by bucket
    - Changing from Set to List on retrieval methods

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

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

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

    https://github.com/apache/nifi-registry/pull/10.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 #10
    
----
commit 8f394aaaabd73bf9a077b5b41ce897015daadac7
Author: Bryan Bende <bbe...@apache.org>
Date:   2017-09-19T14:01:24Z

    NIFIREG-18 Initial plumbling for H2 database
    - Setup Flyway with initial migration to define tables
    - Setup entity classes with repositories
    - Setup unit testing for repositories
    - Removed existing MetadataProvider concept
    - Removed provider impl module and moved remaining pieces into framework
    - Added MetadataService with DatabaseMetadataService implementation
    - Refactored RegistryService to use MetadataService
    - Introduced verbose flag on some end-points to control loading nested 
objects
    - Added ability to pass down paging/sorting params
    - Added endpoints for available fields
    - Adding ItemResource and ability to retrieve all items, or items by bucket
    - Changing from Set to List on retrieval methods

----


> Refactor MetadataProvider to use an embedded database
> -----------------------------------------------------
>
>                 Key: NIFIREG-18
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-18
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Minor
>
> We need to leverage transactions when persisting data to avoid inconsistent 
> states. Currently the MetadataProvider is based on an XML file which doesn't 
> offer much way to rollback an operation. We should switch to using an 
> embedded database.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to