[
https://issues.apache.org/jira/browse/NIFIREG-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173784#comment-16173784
]
ASF GitHub Bot commented on NIFIREG-18:
---------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi-registry/pull/10
@kevdoran I pushed a new commit that changed the repository methods to the
spring-data naming convention, and I removed those two properties that were
being set in the application class which seemed to eliminate the bootstrap
logging, you can still enable the hibernate logging in logback.xml but it will
only go to app log.
> 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)
