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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2012/10/12 15:07:18 UTC

[jira] [Created] (OAK-375) Binaries are kept in memory on write access

Michael Dürig created OAK-375:
---------------------------------

             Summary: Binaries are kept in memory on write access
                 Key: OAK-375
                 URL: https://issues.apache.org/jira/browse/OAK-375
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: core
            Reporter: Michael Dürig
            Assignee: Michael Dürig


When setting binary properties, the binaries are currently kept in memory. It would be better to stream them directly to the Microkernel. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (OAK-375) Binaries are kept in memory on write access

Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OAK-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig resolved OAK-375.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.6

Fixed at revision 1397576
                
> Binaries are kept in memory on write access
> -------------------------------------------
>
>                 Key: OAK-375
>                 URL: https://issues.apache.org/jira/browse/OAK-375
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>             Fix For: 0.6
>
>
> When setting binary properties, the binaries are currently kept in memory. It would be better to stream them directly to the Microkernel. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira