[
https://issues.apache.org/jira/browse/ARROW-12703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Moritz updated ARROW-12703:
-----------------------------------
Description: 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. (was: 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. )
> [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
> Time Spent: 20m
> 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)
