You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Steve Lawrence (JIRA)" <ji...@apache.org> on 2018/01/26 20:09:01 UTC

[jira] [Updated] (DAFFODIL-934) Streaming parser: Need to stream input data in, and infoset out to handle arbitrarily large data.

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

Steve Lawrence updated DAFFODIL-934:
------------------------------------
    Fix Version/s:     (was: 2.1.0)
                   2.2.0
                   2.2.0

> Streaming parser: Need to stream input data in, and infoset out to handle arbitrarily large data.
> -------------------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-934
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-934
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Performance
>    Affects Versions: s13
>            Reporter: Michael Beckerle
>            Priority: Major
>             Fix For: 2.2.0
>
>
> Currently Daffodil requires that all incoming data fit in one java.nio.ByteBuffer. A separate issue (DFDL-881) is about allowing > 4GB files, but data sizes would still be limited by available address space.
> A streaming approach has great advantages. It requires that the input can be streamed in (e.g., from a java.io.InputStream), but also requires that the DFDL Infoset can be streamed out. (Think SAX parser 'events' coming out).  This is complicated by the DFDL notion of points of uncertainty. E.g., until a choice branch has been resolved none of the elements on any branch can be emitted since "backtracking" may invalidate them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)