jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3447) InternalValueFactory should use the DataStore whenever available
Date Thu, 18 Oct 2012 14:08:04 GMT

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

Jukka Zitting updated JCR-3447:
-------------------------------

    Fix Version/s: 2.2.14

Makes sense. Merged also to the 2.2 branch in revision 1399667.
                
> InternalValueFactory should use the DataStore whenever available
> ----------------------------------------------------------------
>
>                 Key: JCR-3447
>                 URL: https://issues.apache.org/jira/browse/JCR-3447
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.2.13, 2.3.7, 2.4.3, 2.5.2
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 2.2.14, 2.4.4, 2.5.3
>
>
> Of the InternalValueFactory methods that create binary values, only {{create(InputStream)}}
currently uses the data store (when configured), while the {{create(byte[])}} and {{create(File)}}
methods don't. This is a bit troublesome since not having large binaries already in the data
store when a session is saved will block all concurrent sessions until the binaries have been
copied to the data store. A better alternative would be to always copy binary values to the
data store as early as possible.

--
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

Mime
View raw message