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.

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

Lazy system tables #4606

Merged
merged 1 commit into from
Dec 13, 2022
Merged

Lazy system tables #4606

merged 1 commit into from
Dec 13, 2022

Conversation

tustvold
Copy link
Contributor

Which issue does this PR close?

Relates to #3777

Rationale for this change

Whilst working on #3777 I discovered somewhat to my surprise that the work of computing system tables is actually done eagerly in SchemaProvider::table. This is at best surprising

What changes are included in this PR?

Adds a StreamingTable that is akin to MemTable but streaming, and then uses this to implement the system tables.

Are these changes tested?

Are there any user-facing changes?

@github-actions github-actions bot added the core Core DataFusion crate label Dec 13, 2022
}
}

impl PartitionStream for InformationSchemaTables {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is significantly less verbose than having to define a TableProvider and then a corresponding ExecutionPlan

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but more verbose than creating a MemTable, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it was the best I could do

/// Construct the `information_schema.tables` virtual table
fn make_tables(&self) -> Arc<dyn TableProvider> {
fn make_tables(&self, builder: &mut InformationSchemaTablesBuilder) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The signature of these is now a little bit strange, but I wanted to try to minimise code movement

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we can refactor them in a follow on PR

Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the rationale for this PR is to defer the information table construction until plan execution rather than during planning?

If so it seems like a good idea to me

// specific language governing permissions and limitations
// under the License.

//! A simplified [`TableProvider`] for streaming partitioned datasets
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the idea that this is the counterpart for MemTable but with deferred execution?

/// Construct the `information_schema.tables` virtual table
fn make_tables(&self) -> Arc<dyn TableProvider> {
fn make_tables(&self, builder: &mut InformationSchemaTablesBuilder) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we can refactor them in a follow on PR

}
}

impl PartitionStream for InformationSchemaTables {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but more verbose than creating a MemTable, right?

@tustvold tustvold merged commit f8a3d58 into apache:master Dec 13, 2022
@ursabot
Copy link

ursabot commented Dec 13, 2022

Benchmark runs are scheduled for baseline = 1c6b143 and contender = f8a3d58. f8a3d58 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Core DataFusion crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants