[
https://issues.apache.org/jira/browse/DAFFODIL-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-1848.
--------------------------------------
Resolution: Won't Fix
This does not appear to be a bug in Daffodil, but is either a bug in the data
or the schema. The data says that there are zero target reports but there are
existence bits set to 1 saying that some fields in the target report exist.
When unparsing, since the these fields do not exist because the target does not
exist, the existence bits are unparsed as zero. It's not clear to me what the
right behavior is, but Daffodil is doing the right thing according to the
schema. Resolving as wont' fix since this is a schema issue and should be
tracked in that file formats bug tracker.
> Unparsed file does not match the source input file, kirkuk_dwellSeg_1.4607
> --------------------------------------------------------------------------
>
> Key: DAFFODIL-1848
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1848
> Project: Daffodil
> Issue Type: Bug
> Components: Unparsing
> Affects Versions: 2.0.0
> Reporter: Dave Thompson
> Priority: Major
> Fix For: 2.3.0
>
>
> The unparsed file does not match (HEX or md5 comparison)��the source test
> file, kirkuk_dwellSeg_1.4607, used in the parse tests.��The HEX comparison is
> shown below. The left is the source file. Same result whether unparsing the
> original or newly created infoset.
> !image-2017-10-03-07-20-18-936.png!
> Note,��the unparsed results of the other small 4607 files match the
> associated source file with md5 hash and HEX comparisons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
