[jira] [Commented] (DAFFODIL-1783) Changing maxFieldContentLengthInBytes does not change Regex limit size

["Steve Lawrence (JIRA)" <ji...@apache.org>]

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

Steve Lawrence commented on DAFFODIL-1783:
------------------------------------------

I'm not sure if this bug is relevant anymore. The maxFieldContentLengthInBytes tunable does not look like it is actually used anywhere. And the maximumRegexMatchLengthInCharacters tuanble is used to put an upper limit on regex match lengths.

Also, the BBSLimits and TLState no longer exists either.

I think the only open question is where maxFieldContentLengthInBytes should be used, if at all.

> Changing maxFieldContentLengthInBytes does not change Regex limit size
> ----------------------------------------------------------------------
>
>                 Key: DAFFODIL-1783
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1783
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>            Reporter: Steve Lawrence
>            Priority: Major
>             Fix For: 2.3.0
>
>
> According to the code, it looks like changing this tunable should allow one to match larger regular expression than the default of 1024 * 1024 characters. But it does not appear to work. Need to investigate. This is seen with a Jpeg2k schema that requires regular expressions that matches many bytes to scan through the data.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)