Hello,
Considering your amazing efficiency on pandas, numpy, and more, it would seem to make sense for your module to work with even bigger data, such as Audio (for example .mp3 and .wav). This is something that would help a lot considering the nature audio (ie. where one of the lowest and most common sampling rates is still 44,100 samples/sec). For a use case, I would consider vaex.open('Hu

This is more a question than a feature request.

When parsing JSON files, I need to sanitize the field names so field with spaces becomes field_with_spaces.
I want to preserve the original name as well, metadata about the column if you like :)

There is a metadata field on StructField, but it is internal.
Why is this internal, is it possible or desirable to expose it?

Dear all,
Volcano v1.1 has been released on Oct 30. Main features such as Big Job Resource Reservation/HDRF/Monitoring are included. More details please refer to https://github.com/volcano-sh/volcano/releases/tag/v1.1.0. Beta test are warmly welcomed and we are looking forward to your advice in issues.
Feature design of v1.2 is alse finished and all main features have been owned. You can

Describe the ideal solution

We need a new endpoint that functions as getIntegrationById endpoint.

Describe your use cases

We currently fetching all integration via appsync (or more specifically a sub-category of integrations based on integrationType) and iterate until we find one that matches the integrationId passed.

How frequently would you use such feature

Although, we

Right now, these aren't caught until we try to gob-encode. Consider failing faster in type-checking to avoid too much confusion/loss when it works with local execution.