You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Olabusayo Kilo (Jira)" <ji...@apache.org> on 2023/04/14 17:44:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Olabusayo Kilo updated DAFFODIL-2802:
-------------------------------------
Description:
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.
For completeness, you get the following error from TDML on the 2nd test
{noformat}
output data length 12 for '/1/2/3.5//6
' doesn't match expected length 13 for '/1/2/3.5///6
'{noformat}
was: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.
> 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.
>
> For completeness, you get the following error from TDML on the 2nd test
> {noformat}
> output data length 12 for '/1/2/3.5//6
> ' doesn't match expected length 13 for '/1/2/3.5///6
> '{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)