Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set increased traversal limit in enumeration deserialization #5365

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

ypatia
Copy link
Member

@ypatia ypatia commented Nov 6, 2024

[sc-58991]

So far we'd only apply an increased traversal limit to the deserialization of certain objects like Query, groups and metadata of all sorts. For the rest of them, like Array Schema evolution we use the default Capnp value that is actually 64MB.

We had a real life scenario where evolving the array schema hit the traversal limit and failed. This is most probably due to the addition of a lot of enumerations in a new schema, and it seems that large enumerations are commonly used in certain scientific use cases. To cope with such cases, this PR sets an increased traversal limit to every deserialization that includes enumerations: schema evolution, array schema and load enumerations response.

TYPE: BUG
DESC: Set increased traversal limit in enumeration deserialization

@ypatia ypatia requested a review from shaunrd0 November 6, 2024 12:21
@ihnorton ihnorton requested a review from Shelnutt2 November 6, 2024 17:08
@ypatia ypatia merged commit 738f238 into dev Nov 7, 2024
64 checks passed
@ypatia ypatia deleted the yt/sc-XXX/increase-schema-evol-travlimit branch November 7, 2024 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants