You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2023/03/08 21:36:00 UTC

[jira] [Commented] (DAFFODIL-2802) Array with optional element followed by scalar optional element drops separator

    [ https://issues.apache.org/jira/browse/DAFFODIL-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17698090#comment-17698090 ] 

Mike Beckerle commented on DAFFODIL-2802:
-----------------------------------------

This is another quite problematic error. There are large schemas for textual data formats OTH-Gold format and USMTF that are much harder to realize without this being fixed. 

The workarounds are quite ugly. 

There seems to be a large number of bugs in this area currently. 

> Array with optional element followed by scalar optional element drops separator
> -------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2802
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2802
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.4.0
>            Reporter: Olabusayo Kilo
>            Priority: Major
>             Fix For: 3.5.0
>
>         Attachments: TestSeparatorSuppression.scala, suppressedseparator.tdml
>
>
> An array with a trailing optional element followed by a scalar optional element loses a separator when both elements are missing during an unparse. The trace indicates, there's a SuppressableSeparatorUnparserSuspendableOperation for the scalar element (se5 in the example schema). My initial guess was that the last element in the array was being treated as a trailing element, but we need it to not be treated that way.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)