[
https://issues.apache.org/jira/browse/OAK-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889507#comment-13889507
]
Tommaso Teofili commented on OAK-834:
-------------------------------------
bq. Added the ReferenceBinaryTest test from Jackrabbit core at
http://svn.apache.org/r1561637. However the test fails since
ReferenceBinary.getReference returns null on Oak.
Is this specific to a certain MK? As I cannot reproduce the failure by just
running the _ValueTestSuite_
bq. Apparently getReference is never null for Jackrabbit. I wonder what the
intended semantics are for Oak. In what cases should that method return
non-null? Always? only when using a certain back-end? Which?
I think it should be not null for all the back-ends that allow to reference a
binary, that in turn means all the back-ends supporting either the DataStore
API or eventually implementing their own mechanism (similar to what's provided
by
http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-core/src/main/java/org/apache/jackrabbit/core/data/AbstractDataStore.java
in combination with
_org.apache.jackrabbit.core.value.ValueFactoryImpl.createValue(Binary)_). So in
the end it may be that the reference String is null for certain back-ends
> Efficient copying of binaries across repositories
> -------------------------------------------------
>
> Key: OAK-834
> URL: https://issues.apache.org/jira/browse/OAK-834
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mk
> Reporter: Tommaso Teofili
> Assignee: Michael Dürig
> Fix For: 0.17
>
>
> As a follow up on JCR-3534 discussions and implementation, we should also
> discuss how to handle a similar scenario in Oak.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
