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

James Turton edited comment on DRILL-8313 at 9/23/22 8:50 AM:
--------------------------------------------------------------

[~pj.fanning] I don't see us getting close to 3Mb. In the RDMBS metastore, jOOQ 
reads a ~300 line database DDL file in YAML format and that, I think, is it. 
While invesitgating I did note that the following library upgrades are possible 
in this module.
{code:java}
    <jooq.version>3.13.6</jooq.version>
    <liquibase.version>4.16.0</liquibase.version>
    <sqlite.version>3.39.3.0</sqlite.version>{code}
Note that trying to upgrade jOOQ beyond 3.13 results in breakage that will 
require code changes.


was (Author: dzamo):
[~pj.fanning] I don't see us getting close to 3Mb. In the RDMBS metastore, jOOq 
reads a ~300 line database DDL file in YAML format and that, I think, is it. 
While invesitgating I did note that the following library upgrades are possible 
in this module.
{code:java}
    <jooq.version>3.13.6</jooq.version>
    <liquibase.version>4.16.0</liquibase.version>
    <sqlite.version>3.39.3.0</sqlite.version>{code}
Note that trying to upgrade jOOQ beyond 3.13 results in breakage that will 
require code changes.

> Introduce configuration for yaml parsing to override the default max file size
> ------------------------------------------------------------------------------
>
>                 Key: DRILL-8313
>                 URL: https://issues.apache.org/jira/browse/DRILL-8313
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: PJ Fanning
>            Priority: Major
>
> snakeyaml 1.32 brings in a default limit of 3Mb when parsing yaml files.
> Need to allow users to specify another value if they need to.
> [https://bitbucket.org/snakeyaml/snakeyaml/src/72dfa9f1074abe2b8a6c8776bee4476b0aed02e3/src/main/java/org/yaml/snakeyaml/LoaderOptions.java]
> I only became aware of this issue in the last few hours.



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

Reply via email to