[ https://issues.apache.org/jira/browse/OAK-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vikas Saurabh updated OAK-6824: ------------------------------- Component/s: run > oak-run console should have some helpers to compose editors based on > repository state > ------------------------------------------------------------------------------------- > > Key: OAK-6824 > URL: https://issues.apache.org/jira/browse/OAK-6824 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: run > Reporter: Vikas Saurabh > Assignee: Vikas Saurabh > Priority: Minor > > Currently, different oak console scripts do a merge using EmptyHook.INSTANCE. > That then requires to take care of various hidden structures which could have > easily been taken care of in-built editors. > That said, I think it'd be useful to only have utilities to compose editors > in scripts - we would most likely _not_ want default behavior (all editors > coming into play) if some recovery is being required via oak-run. > Also, this would be a good point to at least identify some kind of safety > check-list while operating directly on the node-store (or even riskier on > mongo). > /cc [~chetanm] -- This message was sent by Atlassian JIRA (v6.4.14#64029)