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

Tomek Rękawek updated OAK-4307:
-------------------------------
    Description: 
The new {{SegmentWriteOperation#internalWriteStream}} method checks whether the 
input stream to write is a {{SegmentStream}}. If it's, writer will reuse 
existing block ids, rather than storing the whole stream.

It should also check whether the blocks in {{SegmentStream}} comes from the 
same tracker / segment store. Otherwise this will create invalid references if 
someone invokes the {{internalWriteStream()}} method with a {{SegmentStream}} 
created externally.

  was:
The new {{SegmentWriteOperation#internalWriteStream}} method checks whether the 
input stream to write is a {{SegmentStream}}. If it's, writer will reuse 
existing block ids, rather than storing the whole stream.

It should also check whether the blocks in SegmentStream comes from the same 
tracker / segment store. Otherwise this will create invalid references if 
someone invokes the internalWriteStream() method with a SegmentStream created 
externally.


> SegmentWriter saves references to external blobs
> ------------------------------------------------
>
>                 Key: OAK-4307
>                 URL: https://issues.apache.org/jira/browse/OAK-4307
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-next
>            Reporter: Tomek Rękawek
>             Fix For: 1.6
>
>
> The new {{SegmentWriteOperation#internalWriteStream}} method checks whether 
> the input stream to write is a {{SegmentStream}}. If it's, writer will reuse 
> existing block ids, rather than storing the whole stream.
> It should also check whether the blocks in {{SegmentStream}} comes from the 
> same tracker / segment store. Otherwise this will create invalid references 
> if someone invokes the {{internalWriteStream()}} method with a 
> {{SegmentStream}} created externally.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to