You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2019/04/09 10:37:10 UTC

[jira] [Updated] (OAK-7207) Define porcelain and plumbing tools for the Segment Store

     [ https://issues.apache.org/jira/browse/OAK-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davide Giannella updated OAK-7207:
----------------------------------
    Fix Version/s: 1.14.0

> Define porcelain and plumbing tools for the Segment Store
> ---------------------------------------------------------
>
>                 Key: OAK-7207
>                 URL: https://issues.apache.org/jira/browse/OAK-7207
>             Project: Jackrabbit Oak
>          Issue Type: Wish
>          Components: segment-tar
>            Reporter: Francesco Mari
>            Priority: Major
>              Labels: production, tooling
>             Fix For: 1.12.0, 1.14.0
>
>
> In a spirit similar to [Git|https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain]'s, it would be beneficial to create porcelain and plumbing tooling for the Segment Store.
> Plumbing tools expose lower level operations on the Segment Store. Knowledge about the internals of the Segment Store is necessary to understand how plumbing tools work. Plumbing tools communicate via a command line interface. It must be easy to invoke plumbing tools from other tools (possibly by shelling out). The output of plumbing tools must be easy to consume programmatically.
> Porcelain tools are written for human consumption. Their interface must be user-friendly and should be as much as possible backwards compatible. Porcelain tools use plumbing ones to implement their features. It should be possible to use the same porcelain tools with different versions of the plumbing tools, as long as the plumbing tools "speak" through an interface that remain sufficiently compatible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)