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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2017/03/30 14:01:41 UTC

[jira] [Resolved] (OAK-5994) TarWriter could use a slimmer TarEntry object

     [ 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 it.

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
(v6.3.15#6346)