[Legend SQL] Add ability to externalize in arrow format #2716
Conversation
Test Results 562 files - 188 562 suites - 188 28m 47s ⏱️ - 37m 5s For more details on these failures, see this check. Results for commit 3130578. ± Comparison against base commit 6b443d5. ♻️ This comment has been updated with latest results. |
| <dependency> | ||
| <groupId>org.finos.legend.engine</groupId> | ||
| <artifactId>legend-engine-xt-relationalStore-executionPlan</artifactId> | ||
| </dependency> |
There was a problem hiding this comment.
Per my comment on the other PR, we need to avoid bringing specific stores to "core" functionality like externalize. The goal is that externalize works with "any" store, and we need to find a way to dispatch to respective store modules, if we need to.
|
This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days. |
|
This PR was closed because it has been inactive for 35 days. Please re-open if this PR is still relevant. |
What type of PR is this?
Improvement
What does this PR do / why is it needed ?
Allow Alloy SQL clients to request data externalized to arrow format.
This allows users to use a memory efficient serialization format than JSON.
Other notes for reviewers:
Does this PR introduce a user-facing change?