[jira] [Resolved] (DAFFODIL-1735) BLOB/CLOB - large object handles

["Steve Lawrence (Jira)" <ji...@apache.org>]

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

Steve Lawrence resolved DAFFODIL-1735.
--------------------------------------
    Resolution: Fixed

Fixed in commit 9de0d1a3c3d294600d5c769243efe4f67b03bac1

See DAFFODIL-2194 for supporting blobs greater than 2GB. 

> BLOB/CLOB - large object handles
> --------------------------------
>
>                 Key: DAFFODIL-1735
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1735
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: API, Back End, DFDL Language, Front End
>            Reporter: Michael Beckerle
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 2.5.0
>
>
> Binary large object, and character large object (aka BLOB/CLOB) support is needed.
> Rather than transforming a large binary object into hexBinary or string, instead one annotates the DFDL schema to specify that a BLOB/CLOB handle is preferred. The Infoset then contains not the data, but a token/object that can be fed to an "open" API to access a stream of the data. The token/object is a small sized thing. This allows data formats like JPEG 2000 where payloads are often gigabytes.
> Note: implementing this requires revising our ByteBufferDataInputStream layer into one that does not require the input data to fit in memory. 
> See article on Wiki about large objects:  
> https://opensource.ncsa.illinois.edu/confluence/pages/viewpage.action?pageId=54427836



--
This message was sent by Atlassian Jira
(v8.3.2#803003)