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

refactor(output-datatypes): write down the desired behavior for the various output formats #9010

Open
cpcloud opened this issue Apr 18, 2024 · 1 comment
Open

refactor(output-datatypes): write down the desired behavior for the various output formats #9010

cpcloud opened this issue Apr 18, 2024 · 1 comment
Assignees
@cpcloud
Labels
breaking change Changes that introduce an API break at any level refactor Issues or PRs related to refactoring the codebase

Comments

@cpcloud
Copy link
Member

cpcloud commented Apr 18, 2024

We have a lot of issues related to converting execution output to Pandas.

This issue is to track a Ibis-specific specification for how Ibis types map to Pandas types as well as details on edge case handling.
@cpcloud cpcloud added refactor Issues or PRs related to refactoring the codebase breaking change Changes that introduce an API break at any level labels Apr 18, 2024
@cpcloud cpcloud self-assigned this Apr 18, 2024
@kszucs
Copy link
Member

kszucs commented Apr 19, 2024 •
edited
Loading

I think the ideal use case would be to have a well-defined behavior for ibis => pyarrow and rely on pyarrow => pandas to specify ibis => pandas expectations. I successfully use this approach in the chDB backend:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cpcloud cpcloud

Labels
breaking change Changes that introduce an API break at any level refactor Issues or PRs related to refactoring the codebase
Projects
Ibis planning and roadmap
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cpcloud @kszucs