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

The current azure-pipelines.yaml is highly duplicated, especially the Test stages (E2E Tests, E2E Backward Compatibility Tests, and E2E Forward Compatibility Tests).

This should be refactored to remove duplication to make it easy to maintain (e.g, adding a new Spark version to test against).

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature
/help wanted

Description:

Currently, we publish helm chart at https://github.com/volcano-sh/charts and keep helm charts up-to-date at
https://github.com/volcano-sh/volcano/tree/master/installer , and they already mismatched. It's better to make charts as submod of volcano to keep them sync.

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