This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/daffodil-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e1b14ee Publishing from ed62f60bd89cbfa8ca9ecea386af26598d3678e9
e1b14ee is described below
commit e1b14eefa2c4d4f6e911b45944ba34698fa55d66
Author: Apache Daffodil Site Autobuild <[email protected]>
AuthorDate: Thu Sep 3 13:28:44 2026 +0000
Publishing from ed62f60bd89cbfa8ca9ecea386af26598d3678e9
---
content/tunables/index.html | 94 ++++++++++++++++++++++-----------------------
1 file changed, 47 insertions(+), 47 deletions(-)
diff --git a/content/tunables/index.html b/content/tunables/index.html
index c9c6c13..c0ed3fd 100644
--- a/content/tunables/index.html
+++ b/content/tunables/index.html
@@ -110,7 +110,7 @@
Tunables are set by way of the <code class="language-plaintext
highlighter-rouge">tunables</code> element in <a href="/configuration">config
files</a>
or from the <a href="/cli">cli</a> via the <code class="language-plaintext
highlighter-rouge">-T</code> option.</p>
-<h5 id="config-example">Config Example</h5>
+<h2 id="config-example">Config Example</h2>
<div class="language-xml highlighter-rouge"><div class="highlight"><pre
class="highlight"><code> <span class="nt"><daf:dfdlConfig</span>
<span class="na">xmlns:daf=</span><span
class="s">"urn:ogf:dfdl:2013:imp:daffodil.apache.org:2018:ext"</span><span
class="nt">></span>
<span class="nt"><daf:tunables></span>
@@ -123,13 +123,13 @@ or from the <a href="/cli">cli</a> via the <code
class="language-plaintext highl
<p>The config file can then be passed into daffodil subcommands via the <code
class="language-plaintext highlighter-rouge">-c|--config</code> options.</p>
-<h5 id="cli-example">CLI Example</h5>
+<h2 id="cli-example">CLI Example</h2>
<div class="language-bash highlighter-rouge"><div class="highlight"><pre
class="highlight"><code> daffodil parse <span class="nt">-s</span> schema.xsd
<span class="nt">-TsuppressSchemaDefinitionWarnings</span><span
class="o">=</span><span class="s2">"encodingErrorPolicyError"</span> data.bin
</code></pre></div></div>
-<h4 id="definitions">Definitions</h4>
+<h2 id="definitions">Definitions</h2>
-<h5 id="allowexpressionresultcoercion">allowExpressionResultCoercion</h5>
+<h3 id="allowexpressionresultcoercion">allowExpressionResultCoercion</h3>
<p>Defines how Daffodil coerces expressions where the result type differs
from the expected type. As an example, assume the expected type of an
expression is an xs:string, but the expression is { 3 }. In this case, the
@@ -142,7 +142,7 @@ type.</p>
<p>default: true</p>
-<h5 id="allowexternalpathexpressions">allowExternalPathExpressions</h5>
+<h3 id="allowexternalpathexpressions">allowExternalPathExpressions</h3>
<p>By default, path expressions in Daffodil will only work correctly if path
steps are used in an expression defined in the schema when compiled. To
enable the use of other expressions (e.g. during debugging, where not all
@@ -153,56 +153,56 @@ enabled when debugging is enabled.</p>
<p>default: false</p>
-<h5 id="allowlastupsteptoresolvetoarray">allowLastUpStepToResolveToArray</h5>
+<h3 id="allowlastupsteptoresolvetoarray">allowLastUpStepToResolveToArray</h3>
<p>When .. (UpStep) is the last step in an expression, it should only ever
return a single node,
not an array. If true, allow this but issue a warning. If false, issue an SDE.
Note, the value
of true is deprecated, and it might be ignored in future versions.</p>
<p>default: true</p>
-<h5 id="allowsignedintegerlength1bit">allowSignedIntegerLength1Bit</h5>
+<h3 id="allowsignedintegerlength1bit">allowSignedIntegerLength1Bit</h3>
<p>When processing signed binary integers, which should have a length of at
least 2 bits, issue
a warning if the length is less than 2 bits by default, otherwise (if false)
issue a SDE or Processing Error.</p>
<p>default: true</p>
-<h5 id="blobchunksizeinbytes">blobChunkSizeInBytes</h5>
+<h3 id="blobchunksizeinbytes">blobChunkSizeInBytes</h3>
<p>When reading/writing blob data, the maximum number of bytes to read/write
at a time. This is also used when parsing xs:hexBinary data.</p>
<p>default: 4096</p>
-<h5 id="defaultemptyelementparsepolicy">defaultEmptyElementParsePolicy</h5>
+<h3 id="defaultemptyelementparsepolicy">defaultEmptyElementParsePolicy</h3>
<p>Defines the default empty element parse policy to use if it is not defined
in a schema. This is only used if requireEmptyElementParsePolicyProperty is
false.</p>
<p>default: treatAsEmpty</p>
-<h5 id="escalatewarningstoerrors">escalateWarningsToErrors</h5>
+<h3 id="escalatewarningstoerrors">escalateWarningsToErrors</h3>
<p>This tunable allows the escalation of Schema Definition Warnings to
Errors.</p>
<p>default: false</p>
-<h5 id="generatednamespaceprefixstem">generatedNamespacePrefixStem</h5>
+<h3 id="generatednamespaceprefixstem">generatedNamespacePrefixStem</h3>
<p>Stem to use when generating a namespace prefix when one is not defined for
the target naespace.</p>
<p>default: tns</p>
-<h5 id="initialelementoccurrenceshint">initialElementOccurrencesHint</h5>
+<h3 id="initialelementoccurrenceshint">initialElementOccurrencesHint</h3>
<p>Initial array buffer size allocated for recurring elements/arrays.</p>
<p>default: 10</p>
-<h5
id="initialregexmatchlimitincharacters">initialRegexMatchLimitInCharacters</h5>
+<h3
id="initialregexmatchlimitincharacters">initialRegexMatchLimitInCharacters</h3>
<p>Initial number of characters to match when performing regular expression
matches on input data. When a regex fails to match, more data may be
consumed up to the maximumRegexMatchLengthInCharacters tunable.</p>
<p>default: 64</p>
-<h5 id="infosetwalkermode">infosetWalkerMode</h5>
+<h3 id="infosetwalkermode">infosetWalkerMode</h3>
<p>Daffodil can periodically walk the internal infoset to send events to the
configured
InfosetOutputter (streaming) or it can walk the internal infoset once at the
end of
parsing (nonStreaming). The default is "streaming", which keeps memory usage
bounded
@@ -211,7 +211,7 @@ for large infosets. If you want potentially better
performance, set this tunable
<p>default: streaming</p>
-<h5 id="infosetwalkerskipmin">infosetWalkerSkipMin</h5>
+<h3 id="infosetwalkerskipmin">infosetWalkerSkipMin</h3>
<p>If infosetWalkerMode is "streaming", Daffodil periodically walks the
internal infoset to send events to the configured InfosetOutputter,
skipping at least this number of walk attempts. Larger values
@@ -221,7 +221,7 @@ specifically for advanced testing behavior and should not
need to be changed by
<p>default: 32</p>
-<h5 id="infosetwalkerskipmax">infosetWalkerSkipMax</h5>
+<h3 id="infosetwalkerskipmax">infosetWalkerSkipMax</h3>
<p>If infosetWalkerMode is "streaming", Daffodil periodically walks the
internal
infoset to send events to the configured InfosetOutputter. On walks where
no progress is made, the number of walks to skip
@@ -233,13 +233,13 @@ specifically for advanced testing behavior and should not
need to be changed by
<p>default: 2048</p>
-<h5 id="infosetincludedatatype">infosetIncludeDataType</h5>
+<h3 id="infosetincludedatatype">infosetIncludeDataType</h3>
<p>Whether or not to include the dataType infoset member when outputting an
infoset. If
and how this is represented in the infoset is up to InfosetOutputter
implementations.</p>
<p>default: false</p>
-<h5 id="invalidrestrictionpolicy">invalidRestrictionPolicy</h5>
+<h3 id="invalidrestrictionpolicy">invalidRestrictionPolicy</h3>
<p>DFDL only allows a subset of restrictions that XML Schema defines. For
example, DFDL
disallows the use of the xs:pattern restriction on simple types other than
xs:string.
This tunable configures this behavior to allow use of some of these
restrictions. The
@@ -252,54 +252,54 @@ allowed values are:</p>
<p>default: error</p>
-<h5 id="maxbinarydecimalvirtualpoint">maxBinaryDecimalVirtualPoint</h5>
+<h3 id="maxbinarydecimalvirtualpoint">maxBinaryDecimalVirtualPoint</h3>
<p>The largest allowed value of the dfdl:binaryDecimalVirtualPoint
property.</p>
<p>default: 200</p>
-<h5
id="maxbytearrayoutputstreambuffersizeinbytes">maxByteArrayOutputStreamBufferSizeInBytes</h5>
+<h3
id="maxbytearrayoutputstreambuffersizeinbytes">maxByteArrayOutputStreamBufferSizeInBytes</h3>
<p>When unparsing, this is the maximum size of the buffer that the
ByteArrayOutputStream can grow to before switching to a file based
output stream.</p>
<p>default: 2097152000</p>
-<h5 id="maxdatadumpsizeinbytes">maxDataDumpSizeInBytes</h5>
+<h3 id="maxdatadumpsizeinbytes">maxDataDumpSizeInBytes</h3>
<p>The maximum size of data to retrive when when getting data to display
for debugging.</p>
<p>default: 256</p>
-<h5 id="maxhexbinarylengthinbytes">maxHexBinaryLengthInBytes</h5>
+<h3 id="maxhexbinarylengthinbytes">maxHexBinaryLengthInBytes</h3>
<p>The maximum size allowed for an xs:hexBinary element.</p>
<p>default: 1073741823</p>
-<h5
id="maxlengthforvariablelengthdelimiterdisplay">maxLengthForVariableLengthDelimiterDisplay</h5>
+<h3
id="maxlengthforvariablelengthdelimiterdisplay">maxLengthForVariableLengthDelimiterDisplay</h3>
<p>When unexpected text is found where a delimiter is expected, this is the
maximum
number of bytes (characters) to display when the expected delimiter is a
variable
length delimiter.</p>
<p>default: 10</p>
-<h5 id="maxlookaheadfunctionbits">maxLookaheadFunctionBits</h5>
+<h3 id="maxlookaheadfunctionbits">maxLookaheadFunctionBits</h3>
<p>Max distance that the DPath lookahead function is permitted to look.
Distance is defined by the distance to the last bit accessed, and
so it is offset+bitsize.</p>
<p>default: 512</p>
-<h5 id="maxoccursbounds">maxOccursBounds</h5>
+<h3 id="maxoccursbounds">maxOccursBounds</h3>
<p>Maximum number of occurances of an array element.</p>
<p>default: 2147483647</p>
-<h5 id="maxskiplengthinbytes">maxSkipLengthInBytes</h5>
+<h3 id="maxskiplengthinbytes">maxSkipLengthInBytes</h3>
<p>Maximum number of bytes allowed to skip in a skip region.</p>
<p>default: 1024</p>
-<h5 id="maxvalidyear">maxValidYear</h5>
+<h3 id="maxvalidyear">maxValidYear</h3>
<p>Due to differences in the DFDL spec and ICU4J SimpleDateFormat, we must
have SimpleDateFormat parse in lenient mode, which allows the year value
to overflow with very large years into possibly negative years. This
@@ -307,23 +307,23 @@ tunable tunable sets an upper limit for values to prevent
overflow.</p>
<p>default: 9999</p>
-<h5
id="maximumregexmatchlengthincharacters">maximumRegexMatchLengthInCharacters</h5>
+<h3
id="maximumregexmatchlengthincharacters">maximumRegexMatchLengthInCharacters</h3>
<p>Maximum number of characters to match when performing regular expression
matches on input data.</p>
<p>default: 1048576</p>
-<h5
id="maximumsimpleelementsizeincharacters">maximumSimpleElementSizeInCharacters</h5>
+<h3
id="maximumsimpleelementsizeincharacters">maximumSimpleElementSizeInCharacters</h3>
<p>Maximum number of characters to parse when parsing string data.</p>
<p>default: 1048576</p>
-<h5 id="minbinarydecimalvirtualpoint">minBinaryDecimalVirtualPoint</h5>
+<h3 id="minbinarydecimalvirtualpoint">minBinaryDecimalVirtualPoint</h3>
<p>The smallest allowed value of the dfdl:binaryDecimalVirtualPoint
property.</p>
<p>default: -200</p>
-<h5 id="minvalidyear">minValidYear</h5>
+<h3 id="minvalidyear">minValidYear</h3>
<p>Due to differences in the DFDL spec and ICU4J SimpleDateFormat, we must
have SimpleDateFormat parse in lenient mode, which allows the year value
to overflow with very large years into possibly negative years. This
@@ -331,20 +331,20 @@ tunable tunable sets an upper limit for values to prevent
underflow.</p>
<p>default: 0</p>
-<h5 id="outputstreamchunksizeinbytes">outputStreamChunkSizeInBytes</h5>
+<h3 id="outputstreamchunksizeinbytes">outputStreamChunkSizeInBytes</h3>
<p>When writing file data to the output stream during unparse, this
is the maximum number of bytes to write at a time.</p>
<p>default: 65536</p>
-<h5 id="parseunparsepolicy">parseUnparsePolicy</h5>
+<h3 id="parseunparsepolicy">parseUnparsePolicy</h3>
<p>Whether to compile a schema to support only parsing, only unparsing, both,
or to
use the daf:parseUnparsePolicy from the root node. All child elements of the
root
must have a compatable daf:parseUnaprsePolicy property.</p>
<p>default: fromRoot</p>
-<h5 id="releaseunneededinfoset">releaseUnneededInfoset</h5>
+<h3 id="releaseunneededinfoset">releaseUnneededInfoset</h3>
<p>Daffodil will periodically release internal infoset elements that it
determines
are no longer needed, thus freeing memory. Setting this value to false will
prevent this from taking place. This should usually only be used while
debugging
@@ -352,44 +352,44 @@ or with very specific tests.</p>
<p>default: true</p>
-<h5 id="requirebitorderproperty">requireBitOrderProperty</h5>
+<h3 id="requirebitorderproperty">requireBitOrderProperty</h3>
<p>If true, require that the dfdl:bitOrder property is specified. If false,
use a
default value if the property is not defined in the schema.</p>
<p>default: false</p>
-<h5
id="requireemptyelementparsepolicyproperty">requireEmptyElementParsePolicyProperty</h5>
+<h3
id="requireemptyelementparsepolicyproperty">requireEmptyElementParsePolicyProperty</h3>
<p>If true, require that the dfdl:emptyElementParsePolicy property is
specified in
the schema. If false, and not defined in the schema, uses the
defaultEmptyElementParsePolicy as the value of emptyElementParsePolicy.</p>
<p>default: false</p>
-<h5
id="requireencodingerrorpolicyproperty">requireEncodingErrorPolicyProperty</h5>
+<h3
id="requireencodingerrorpolicyproperty">requireEncodingErrorPolicyProperty</h3>
<p>If true, require that the dfdl:encodingErrorPolicy property is specified. If
false, use a default value if the property is not defined in the schema.</p>
<p>default: false</p>
-<h5 id="requirefloatingproperty">requireFloatingProperty</h5>
+<h3 id="requirefloatingproperty">requireFloatingProperty</h3>
<p>If true, require that the dfdl:floating property is specified. If
false, use a default value if the property is not defined in the schema.</p>
<p>default: false</p>
-<h5 id="requiretextbidiproperty">requireTextBidiProperty</h5>
+<h3 id="requiretextbidiproperty">requireTextBidiProperty</h3>
<p>If true, require that the dfdl:testBidi property is specified. If
false, use a default value if the property is not defined in the schema.</p>
<p>default: false</p>
-<h5 id="requiretextstandardbaseproperty">requireTextStandardBaseProperty</h5>
+<h3 id="requiretextstandardbaseproperty">requireTextStandardBaseProperty</h3>
<p>If true, require that the dfdl:textStandardBase property is specified. If
false
and the property is missing, behave as if the property is set to 10.</p>
<p>default: false</p>
-<h5 id="saxunparseeventbatchsize">saxUnparseEventBatchSize</h5>
+<h3 id="saxunparseeventbatchsize">saxUnparseEventBatchSize</h3>
<p>Daffodil's SAX Unparse API allows events to be batched in memory to
minimize the
frequency of context switching between the SAXInfosetInputter thread that
processes
the events, and the DaffodilUnparseContentHandler thread that generates the
events.
@@ -399,20 +399,20 @@ frequency of context switching, but increase the memory
footprint.</p>
<p>default: 100</p>
-<h5 id="suppressschemadefinitionwarnings">suppressSchemaDefinitionWarnings</h5>
+<h3 id="suppressschemadefinitionwarnings">suppressSchemaDefinitionWarnings</h3>
<p>Space-separated list of schema definition warnings that should be ignored,
or "all" to ignore all warnings.</p>
<p>default: emptyElementParsePolicyError</p>
-<h5 id="tempfilepath">tempFilePath</h5>
+<h3 id="tempfilepath">tempFilePath</h3>
<p>When unparsing, use this path to store temporary files that may be genrated.
The default value (empty string) will result in the use of the java.io.tmpdir
property being used as the path.</p>
<p>default: This string is ignored. Default value is taken from java.io.tmpdir
property</p>
-<h5 id="unqualifiedpathsteppolicy">unqualifiedPathStepPolicy</h5>
+<h3 id="unqualifiedpathsteppolicy">unqualifiedPathStepPolicy</h3>
<p>Defines how to lookup DFDL expression path steps that to not include a
namespace prefix. Values are:</p>
<ul>
@@ -424,7 +424,7 @@ if non are found, match elemnts that do not have a
namespace</li>
<p>default: noNamespace</p>
-<h5 id="unparsesuspensionwaitold">unparseSuspensionWaitOld</h5>
+<h3 id="unparsesuspensionwaitold">unparseSuspensionWaitOld</h3>
<p>While unparsing, some unparse actions require "suspending" which
requires buffering unparse output until the suspension can be
evaluated. Daffodil periodically attempts to reevaluate these
@@ -441,12 +441,12 @@ young and old suspensions, respectively.</p>
<p>default: 100</p>
-<h5 id="unparsesuspensionwaityoung">unparseSuspensionWaitYoung</h5>
+<h3 id="unparsesuspensionwaityoung">unparseSuspensionWaitYoung</h3>
<p>See unparseSuspensionWaitOld</p>
<p>default: 5</p>
-<h4 id="deprecated">Deprecated</h4>
+<h2 id="deprecated">Deprecated</h2>
<ul>
<li>allowBigIntegerBits</li>
<li>defaultInitialRegexMatchLimitInChars</li>
