You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Dominik Moritz (Jira)" <ji...@apache.org> on 2021/06/03 01:54:00 UTC

[jira] [Resolved] (ARROW-12703) [JS] Separate Table from DataFrame

     [ https://issues.apache.org/jira/browse/ARROW-12703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Moritz resolved ARROW-12703.
------------------------------------
    Fix Version/s: 5.0.0
       Resolution: Fixed

Issue resolved by pull request 10277
[https://github.com/apache/arrow/pull/10277]

> [JS] Separate Table from DataFrame
> ----------------------------------
>
>                 Key: ARROW-12703
>                 URL: https://issues.apache.org/jira/browse/ARROW-12703
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: JavaScript
>            Reporter: Dominik Moritz
>            Assignee: Dominik Moritz
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 5.0.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> A DataFrame should be a valid table but not vice versa. Then one can use a Table without also pulling in all the compute functionality. We can then extend the compute functionality without incurring larger bundle sizes. Another advantage is that we could support compiled expressions in the compute code but people could build bundles without it that run on environments with CSP. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)