[
https://issues.apache.org/jira/browse/ASTERIXDB-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954635#comment-17954635
]
ASF subversion and git services commented on ASTERIXDB-3609:
------------------------------------------------------------
Commit d494c311107da4d21a17dd9d2f6cde5f04b8d969 in asterixdb's branch
refs/heads/master from Ian Maxon
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=d494c31110 ]
[ASTERIXDB-3609][API][RT] Library archive limits
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
Library archives might be highly compressed or have
a very high number of entries. We should check for
these conditions when extracting them and make sure
they conform to reasonable limits for the use cases
we expect.
Ext-ref: MB-66704
Change-Id: I524cbfb6685bd3c1e326ad2db48482e5aba1ce6d
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19771
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Ian Maxon <[email protected]>
Reviewed-by: Peeyush Gupta <[email protected]>
> Libraries should constrain archives to certain size limits
> ----------------------------------------------------------
>
> Key: ASTERIXDB-3609
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3609
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: API - HTTP API, RT - Runtime
> Reporter: Ian Maxon
> Assignee: Ian Maxon
> Priority: Major
> Labels: triaged
>
> Currently the library API doesn't check if zip archives might contain large
> entries, or a great deal of entries, or a very large amount of data. This
> should be checked just like the extracted path.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
