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

Minor: refine Partitioning documentation #12145

Merged
merged 1 commit into from
Aug 26, 2024

Conversation

alamb
Copy link
Contributor

@alamb alamb commented Aug 24, 2024

Which issue does this PR close?

Closes #.

Rationale for this change

I was looking for the page on Partitioning but the first
thing that comes up is the partitioning description for Logical plans

Screenshot 2024-08-24 at 5 27 42 AM

Thus I would like to link the description in the result that also appears first

What changes are included in this PR?

Add a link from logical Partitioning to the more detailed documentation

Here is what the doc looks like now:

Screenshot 2024-08-24 at 5 30 30 AM

Are these changes tested?

By doc CI and I also looked at it manually

Are there any user-facing changes?

@github-actions github-actions bot added logical-expr Logical plan and expressions physical-expr Physical Expressions labels Aug 24, 2024
@@ -24,8 +24,8 @@ use crate::{physical_exprs_equal, EquivalenceProperties, PhysicalExpr};

/// Output partitioning supported by [`ExecutionPlan`]s.
///
/// When `executed`, `ExecutionPlan`s produce one or more independent stream of
/// data batches in parallel, referred to as partitions. The streams are Rust
/// Calling [`ExecutionPlan::execute`] produce one or more independent streams of
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 was a driveby cleanup

/// Logical partitioning schemes supported by the repartition operator.
/// Logical partitioning schemes supported by [`LogicalPlan::Repartition`]
///
/// See [`Partitioning`] for more details on partitioning
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 main reason for this PR is to add this link

/// When `executed`, `ExecutionPlan`s produce one or more independent stream of
/// data batches in parallel, referred to as partitions. The streams are Rust
/// Calling [`ExecutionPlan::execute`] produce one or more independent streams of
/// [`RecordBatch`]es in parallel, referred to as partitions. The streams are Rust
/// `async` [`Stream`]s (a special kind of future). The number of output
Copy link
Contributor

Choose a reason for hiding this comment

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

perhaps we can add the link to the futures-core crate which backs streams ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I double checked by building the docs locally

This link looks like this:
Screenshot 2024-08-25 at 6 59 37 AM

And it goes to this link:
https://docs.rs/futures/latest/futures/stream/trait.Stream.html

Is that what you mean by link to futures-core? Or do you mean something else?

Copy link
Contributor

Choose a reason for hiding this comment

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

exactly, my bad, when I navigated from IDE it showed me the crate name as futures-core sub crate which is confusing

Copy link
Contributor

@comphead comphead left a comment

Choose a reason for hiding this comment

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

lgtm thanks @alamb

@alamb
Copy link
Contributor Author

alamb commented Aug 26, 2024

Thanks @comphead

@alamb alamb merged commit 7d49fb3 into apache:main Aug 26, 2024
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
logical-expr Logical plan and expressions physical-expr Physical Expressions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants