You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2020/12/02 15:20:00 UTC

[jira] [Closed] (DAFFODIL-2412) CLI unparse command always reads infoset into a byte array

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

Dave Thompson closed DAFFODIL-2412.
-----------------------------------

Verified the specified commit (commit 45934b73fbbeab65594165406cee85e744a25ca2) is included in the latest pull from the incubator-daffodil repository.

Verified the all incubator-daffodil sbt test suites execute successfully including the added tests.

Verified the nightly test schemas compile and save successfully.

Verified the nightly test suite executes successfully for each infoset format.

> CLI unparse command always reads infoset into a byte array
> ----------------------------------------------------------
>
>                 Key: DAFFODIL-2412
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2412
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: CLI
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 3.0.0
>
>
> The CLI currently always reads the entire infoset into an ByteArray. This means it cannot unparse infosets that are larger than memory. For the performance command, this might be reasonable since we want to avoid any overhead relted to reading from disk. But for the normal unparse commad using an the "xml" infoset type, we should be able to unparse directly from the InputStream.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)