jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3534) Add JackrabbitSession.getValueByContentId method
Date Fri, 15 Mar 2013 13:52:13 GMT
Felix Meschberger created JCR-3534:
--------------------------------------

             Summary: Add JackrabbitSession.getValueByContentId method
                 Key: JCR-3534
                 URL: https://issues.apache.org/jira/browse/JCR-3534
             Project: Jackrabbit Content Repository
          Issue Type: New Feature
            Reporter: Felix Meschberger


we have a couple of use cases, where we would like to leverage the global data store to prevent
sending around and copying around large binary data unnecessarily: We have two separate Jackrabbit
instances configured to use the same DataStore (for the sake of this discussion assume we
have the problems of concurrent access and garbage collection under control). When sending
content from one instance to the other instance we don't want to send potentially large binary
data (e.g. video files) if not needed.

The idea is for the sender to just send the content identity from JackrabbitValue.getContentIdentity().
The receiver would then check whether the such content already exists and would reuse if so:

String ci = contentIdentity_from_sender;
try {
    Value v = session.getValueByContentIdentity(ci);
    Property p = targetNode.setProperty(propName, v);
} catch (ItemNotFoundException ie) {
    // unknown or invalid content Identity
} catch (RepositoryException re) {
    // some other exception
}

Thus the proposed JackrabbitSession.getValueByContentIdentity(String) method would allow for
round tripping the JackrabbitValue.getContentIdentity() preventing superfluous binary data
copying and moving. 

See also the dev@ thread http://jackrabbit.markmail.org/thread/gedk5jsrp6offkhi

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