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

[CHORE] Remove existing LogicalPlan from all execution concepts #1208

Merged
merged 11 commits into from
Aug 2, 2023

Conversation

xcharleslin
Copy link
Contributor

@xcharleslin xcharleslin commented Aug 1, 2023

Currently, a lot of query fragment executors are parameterized by a LogicalPlan node object, since it holds relevant subfields. This is not necessary; the executors can be parameterized by the subfields directly.

This PR removes LogicalPlan from all query execution concepts.

  1. This is necessary in order to switch to a new logical plan implementation.
  2. It will also provide an immediate performance boost, since redundant information (often an entire plan subtree) is not serialized with the execution information anymore.

@codecov
Copy link

codecov bot commented Aug 1, 2023

Codecov Report

Merging #1208 (023ae28) into main (e681536) will decrease coverage by 0.11%.
The diff coverage is 93.22%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1208      +/-   ##
==========================================
- Coverage   88.41%   88.31%   -0.11%     
==========================================
  Files          55       55              
  Lines        5620     5630      +10     
==========================================
+ Hits         4969     4972       +3     
- Misses        651      658       +7     
Files Changed Coverage Δ
daft/execution/execution_step.py 93.90% <92.30%> (-0.17%) ⬇️
daft/execution/physical_plan.py 94.60% <92.85%> (-2.48%) ⬇️
daft/execution/physical_plan_factory.py 93.10% <100.00%> (ø)

... and 1 file with indirect coverage changes

@@ -5,6 +5,8 @@
from dataclasses import dataclass, field
from typing import Generic, TypeVar

import fsspec
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be behind a TYPE_CHECKING guard since fsspec is an optional dependency.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

thank you, done!

@@ -17,8 +17,10 @@
from collections import deque
from typing import Generator, Iterator, TypeVar, Union

import fsspec
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here.

@xcharleslin xcharleslin marked this pull request as ready for review August 1, 2023 23:58
Copy link
Contributor

@clarkzinzow clarkzinzow left a comment

Choose a reason for hiding this comment

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

LGTM! 🙌

@xcharleslin xcharleslin merged commit fdd74f2 into main Aug 2, 2023
18 checks passed
@xcharleslin xcharleslin deleted the charles/remove-logplan-from-physplan branch August 2, 2023 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants