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.

Sign up for GitHub

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

Jump to bottom

[Docs] Include nanoarrow in the Implementation Status docs page #40689

Closed
ianmcook opened this issue Mar 20, 2024 · 3 comments
Closed

[Docs] Include nanoarrow in the Implementation Status docs page #40689

ianmcook opened this issue Mar 20, 2024 · 3 comments
Assignees
@paleolimbot
Labels
Component: Documentation Type: enhancement
Milestone
16.0.0

Comments

@ianmcook
Copy link
Member

ianmcook commented Mar 20, 2024 •
edited
Loading

Describe the enhancement requested

For some of the sections on the Implementation Status page, we should include a column for nanoarrow.

@paleolimbot @jorisvandenbossche

Component(s)

Documentation
@ianmcook
Copy link
Member Author

One challenge with this is that nanoarrow now has language bindings and isn't just a C library. I'm not sure how we would render this in the Implementation Status. Maybe the column for nanoarrow could just represent the nanoarrow C library, and there could be footnotes referring to places where the nanoarrow bindings lag behind the nanoarrow C library.

@paleolimbot
Copy link
Member

Thanks for opening this! I can take this on...I agree that representing the C library is the best approach. The R and Python bindings have the extra feature of being able to convert to/from existing R/Python types; however, can build or consume any type (supported by the C library) from/to buffers.

@github-actions github-actions bot mentioned this issue Apr 6, 2024
Merged
paleolimbot added a commit that referenced this issue Apr 9, 2024
@paleolimbot
GH-40689: [Docs] Add nanoarrow to implementation status page (#41052)
dbedcfc 
### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: #40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
@paleolimbot paleolimbot added this to the 16.0.0 milestone Apr 9, 2024
@paleolimbot
Copy link
Member

Issue resolved by pull request 41052
#41052

raulcd pushed a commit that referenced this issue Apr 10, 2024
@paleolimbot @raulcd
GH-40689: [Docs] Add nanoarrow to implementation status page (#41052)
93d2db0 
### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: #40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
verma-kartik pushed a commit to verma-kartik/arrow that referenced this issue Apr 11, 2024
@paleolimbot @verma-kartik
apacheGH-40689: [Docs] Add nanoarrow to implementation status page (a…
2ea4453 
…pache#41052)

### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: apache#40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
vibhatha pushed a commit to vibhatha/arrow that referenced this issue Apr 15, 2024
@paleolimbot @vibhatha
apacheGH-40689: [Docs] Add nanoarrow to implementation status page (a…
963ba9a 
…pache#41052)

### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: apache#40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
tolleybot pushed a commit to tmct/arrow that referenced this issue May 2, 2024
@paleolimbot @tolleybot
apacheGH-40689: [Docs] Add nanoarrow to implementation status page (a…
4918f11 
…pache#41052)

### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: apache#40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
tolleybot pushed a commit to tmct/arrow that referenced this issue May 4, 2024
@paleolimbot @tolleybot
apacheGH-40689: [Docs] Add nanoarrow to implementation status page (a…
0d2e671 
…pache#41052)

### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: apache#40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
rok pushed a commit to tmct/arrow that referenced this issue May 8, 2024
@paleolimbot @rok
apacheGH-40689: [Docs] Add nanoarrow to implementation status page (a…
c0093fc 
…pache#41052)

### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: apache#40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
rok pushed a commit to tmct/arrow that referenced this issue May 8, 2024
@paleolimbot @rok
apacheGH-40689: [Docs] Add nanoarrow to implementation status page (a…
dc5de5d 
…pache#41052)

### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: apache#40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
vibhatha pushed a commit to vibhatha/arrow that referenced this issue May 25, 2024
@paleolimbot @vibhatha
apacheGH-40689: [Docs] Add nanoarrow to implementation status page (a…
9f7e334 
…pache#41052)

### Rationale for this change

nanoarrow now supports most types and reading IPC streams. As discussed in the issue, there is interest in adding it to the implementation status page for visibility.

### What changes are included in this PR?

A column was added to the table with the appropriate values characterizing the C library implementation status.

### Are these changes tested?

Not needed (docs!)

### Are there any user-facing changes?

No (docs!)
* GitHub Issue: apache#40689

Lead-authored-by: Dewey Dunnington <dewey@voltrondata.com>
Co-authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Dewey Dunnington <dewey@fishandwhistle.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paleolimbot paleolimbot

Labels
Component: Documentation Type: enhancement
Projects
None yet
Milestone
16.0.0
Development

No branches or pull requests
2 participants
@ianmcook @paleolimbot