-
Notifications
You must be signed in to change notification settings - Fork 928
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
docs/nodes-grouping #4519
base: main
Are you sure you want to change the base?
docs/nodes-grouping #4519
Conversation
Signed-off-by: Huong Nguyen <[email protected]>
Thanks for the PR, @Huongg - great job! Here are a few initial comments:
![]() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The general content looks good to me, but I'm not sure the table is the right format. It's quite small and the bullet points aren't formatted nicely inside the columns. Perhaps you can just write the content inside paragraphs with clear headings?
I've also left some comments on the phrasing, I find the tone of the text a bit too marketing style, like we're trying to sell this feature instead of explaining it. I'd suggest changing the tone to make it more informative and explain the why more than the what.
Signed-off-by: Huong Nguyen <[email protected]>
Signed-off-by: Huong Nguyen <[email protected]>
Signed-off-by: Huong Nguyen <[email protected]>
7fae928
to
53dae3c
Compare
Signed-off-by: Huong Nguyen <[email protected]>
Signed-off-by: Huong Nguyen <[email protected]>
Signed-off-by: Huong Nguyen <[email protected]>
Signed-off-by: Huong Nguyen <[email protected]>
hey @DmitrySorokinQB and @merelcht thanks for reviewing this PR! I agree that the table format was quite hard to read in this form. I've updated it to use paragraphs instead, but I've also included a summary table at the end to highlight the key points and make it easier for users. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @Huongg and team! Left a few comments.
More broadly, the "what works in Kedro - what doesn't work in Kedro - how to use" section titles feel a bit repetitive, but the "best used when - not to use when" are useful. Maybe when we're settled on the content we can turn some of these bullet lists into prose?
@@ -36,6 +36,11 @@ This following pages provide information for deployment to, or integration with, | |||
* [Prefect](prefect.md) | |||
* [Vertex AI](vertexai.md) | |||
|
|||
|
|||
# Effective node grouping for deployment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Effective node grouping for deployment | |
## Effective node grouping for deployment |
There's something funky happening with the navigation bar with these pages 🤔
Compare https://docs.kedro.org/en/nightly/
with this PR
maybe turning this into an H2 will fix it
``` {warning} | ||
We also have legacy documentation pages for the following deployment targets, but these have not been tested against recent Kedro releases and we cannot guarantee them: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to move this warning before the "effective node grouping" section
 | ||
|
||
### What doesn't work with Kedro | ||
- If you need to create custom node groupings that are different with your existing pipelines, creating new pipelines for them may not be convenient. Instead, you can use alternative grouping methods such as tags or namespaces. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't quite understand this sentence 🤔
### What doesn't work with Kedro | ||
- If you need to create custom node groupings that are different with your existing pipelines, creating new pipelines for them may not be convenient. Instead, you can use alternative grouping methods such as tags or namespaces. | ||
- You cannot execute more than one pipeline in a single step because the kedro run --pipeline command allows running one pipeline at a time. | ||
- You can switch between different pipelines in Kedro Viz, but the visualisation does not support collapsing or expanding pipelines within Kedro Viz. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- You can switch between different pipelines in Kedro Viz, but the visualisation does not support collapsing or expanding pipelines within Kedro Viz. | |
- You can switch between different pipelines in Kedro Viz, but the flowchart view does not support collapsing or expanding pipelines. |
?
|
||
### What doesn't work with Kedro | ||
- Nodes with the same tag can exist in different pipelines, making debugging and maintaining the codebase more challenging. | ||
- Executing more than one tag in a single step isn't always possible, and sometimes it will fail to run if a part of pipeline is not populated before at the time of execution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this part of every method though? For example, if I run kedro run --pipeline data_science
before data_processing
, it will fail, would it not?
- Tags are not hierarchical, so tracking groups of nodes can become difficult. | ||
- Tags do not enforce structure like pipelines or namespaces. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two are they key ones I think 💯
### What works with Kedro | ||
- Namespaces allow you to group nodes, ensuring clear dependencies and separation within a pipeline while maintaining a consistent structure. | ||
- As the same as pipelines or tags, you can enable selective execution using namespaces. | ||
- Namespaces improve visualisation in Kedro-Viz. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe "Kedro Viz supports expand and collapsing namespaces as nested pipelines" or sth like that?
- **Defining namespace at Pipeline-level:** When applying a namespace at the pipeline level, Kedro automatically renames all inputs, outputs, and parameters within that pipeline. This can introduce naming conflicts. | ||
|
||
### Best used when | ||
- You want to organise nodes logically within a pipeline while keeping a structured execution flow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could mention that namespaces allow nesting?
Co-authored-by: Juan Luis Cano Rodríguez <[email protected]> Signed-off-by: Huong Nguyen <[email protected]>
Co-authored-by: Juan Luis Cano Rodríguez <[email protected]> Signed-off-by: Huong Nguyen <[email protected]>
Co-authored-by: Merel Theisen <[email protected]> Signed-off-by: Huong Nguyen <[email protected]>
Co-authored-by: Merel Theisen <[email protected]> Signed-off-by: Huong Nguyen <[email protected]>
Co-authored-by: Merel Theisen <[email protected]> Signed-off-by: Huong Nguyen <[email protected]>
Description
The first draft for nodes grouping documentation. Content is TBC by the team.
closes #4441
Development notes
Developer Certificate of Origin
We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a
Signed-off-by
line in the commit message. See our wiki for guidance.If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.
Checklist
RELEASE.md
file