Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[JS][C Data Interface] Use wasm memory pool and expose C interface

Open
#82 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, typescript, wasm
Domain
api, data, web-dev

Research direction

The issue concerns the Arrow JavaScript API, the C Data interface, WebAssembly memory, and C++ signatures, but names no files, tests, or entry points. Start by locating the JavaScript memory-pool and C Data interface bindings; the requested outcome is a feasibility/design determination or measurements of copying latency and memory usage.

Written by the indexing model from the issue text.

Description

Type: usage
Describe the usage question you have. Please include as many useful details as possible.

Hi, I'd like to use the Arrow Javascript API with the C Data interface and webassembly to do the following:

  1. Fetch / create Tables and/or RecordBatch from JS, but using wasm memory (I didn't see a memory pool option in JS - is that on the roadmap?)
  2. Call wasm functions that have the Arrow C Data interface in their signatures, in order to zero-copy access the Tables / RecordBatch from wasm C++.

Are there development plans that would enable this? If not, I'd like to test out the latency and memory usage of copying Arrow Tables / RecordBatch into wasm memory, and making them available to the same C Data interface functions.

@domoritz you seem to think about these sorts of interfaces / designs - have any pointers? Thanks!

Component(s)

JavaScript

Dominant language
TypeScript
Stars
112
Forks
23
Avg merge
17h 55m
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-js

All issues in apache/arrow-js

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.