[ https://issues.apache.org/jira/browse/NIFIREG-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173742#comment-16173742 ]
ASF GitHub Bot commented on NIFIREG-18: --------------------------------------- Github user bbende commented on a diff in the pull request: https://github.com/apache/nifi-registry/pull/10#discussion_r140073748 --- Diff: nifi-registry-resources/src/main/resources/conf/logback.xml --- @@ -68,6 +68,11 @@ <logger name="org.apache.nifi.registry" level="INFO"/> + <!-- To see SQL statements set this to DEBUG --> + <logger name="org.hibernate.SQL" level="INFO" /> + <!-- To see the values in SQL statements set this to TRACE --> + <logger name="org.hibernate.type" level="INFO" /> + --- End diff -- Good find, will investigate > 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)