jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-5994) TarWriter could use a slimmer TarEntry object
Date Thu, 30 Mar 2017 14:01:41 GMT

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

Alex Parvulescu resolved OAK-5994.
       Resolution: Later
    Fix Version/s:     (was: 1.7.0)

bq. Those light entries only affect the TarWriter AFAICS. Given that we shouldn't have significantly
more than 1000 entries by segment I am a bit sceptical whether the savings are actually worth

yes. fully agree, maybe the marginal savings don't justify the change. resolving as 'later'.

> TarWriter could use a slimmer TarEntry object
> ---------------------------------------------
>                 Key: OAK-5994
>                 URL: https://issues.apache.org/jira/browse/OAK-5994
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>            Priority: Minor
> TarWriter uses a full TarEntry for the index, but there is some information that is duplicated
between the index keys and the index values themselves, so I propose to remove this duplication
by introducing a lite version of the TarEntry class.

This message was sent by Atlassian JIRA

View raw message