[
https://issues.apache.org/jira/browse/DAFFODIL-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2880.
-----------------------------------
Verified the specified commit (commit 9b12912f59140b1e934133e777a616b6f8fff702)
is included in the latest pull from the daffodil repository.
Verified, via review, changes identified in the commit comment were
implemented.
Verified the affected daffodil subproject sbt test suites executed
successfully, including the added test.
Verified that if the -T (tunable) option is used in daffodil performance, parse
or unparse commands, results in the error message "[error] Option 'parser'
conflicts with option 'T'".
> CLI tunable option does not have an affect using saved parser -- needs
> error/warning
> ------------------------------------------------------------------------------------
>
> Key: DAFFODIL-2880
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2880
> Project: Daffodil
> Issue Type: Bug
> Components: CLI
> Reporter: Steve Lawrence
> Priority: Minor
> Fix For: 3.7.0
>
>
> When using the CLI with the --parser option to use a saved parser, the -T
> option to set tunables has no affect. Instead, Daffodil uses the values of
> tunables set at schema compilation time.
> This is probably the correct behavior since it could potentially cause odd
> behavior to have different tunables for schema compilation and schema
> parsing, but there is no warning or error message that they are ignored and
> have no affect. So Daffodil just silently ignores the tunable values, which
> can be confusing if you are expecting a different behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
