-
Notifications
You must be signed in to change notification settings - Fork 6
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
[API-2108]UCD Documentation #10
Conversation
✅ Deploy Preview for eclectic-sawine-19fcf1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
The stages of a Jet job can be defined with in a yaml file without any Java code interaction. A basic streaming job consists of two or more stages. These are source, transform and sink stages. The transformation stage is optional, and a pipeline can have multiple transformation steps. In order to define these stages for your job, you can benefit from a yaml definition without any coding effort. | ||
|
||
NOTE: This feature is only available if your cluster is running on Viridian. |
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.
Not keen on documenting Viridian within Platform, but this is a current issue across the docs.
We maybe ought to consider a single source with partials across the docs - but this would be a much bigger update to achieve.
For now, I suggest we retain this Viridian-specific information in the Platform docs for this update and address the issue as part of the larger docs improvements.
(sorry, this is a note for @hazelcast/documentation and can be ignored for this review)
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.
Just two trivial ideas, will continue to review.
@@ -0,0 +1,542 @@ | |||
= YAML Job Definition | |||
|
|||
The stages of a Jet job can be defined with in a yaml file without any Java code interaction. A basic streaming job consists of two or more stages. These are source, transform and sink stages. The transformation stage is optional, and a pipeline can have multiple transformation steps. In order to define these stages for your job, you can benefit from a yaml definition without any coding effort. |
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 stages of a Jet job can be defined with in a yaml file without any Java code interaction. A basic streaming job consists of two or more stages. These are source, transform and sink stages. The transformation stage is optional, and a pipeline can have multiple transformation steps. In order to define these stages for your job, you can benefit from a yaml definition without any coding effort. | |
The stages of a Jet pipeline can be defined with in a yaml file without any Java code interaction. A basic streaming job consists of two or more stages. These are source, transform and sink stages. The transformation stage is optional, and a pipeline can have multiple transformation steps. In order to define these stages for your job, you can benefit from a yaml definition without any coding effort. |
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: Yüce Tekol <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
Co-authored-by: rebekah-lawrence <[email protected]>
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.
LGTM
Let's please not merge this one until the following PR is reviewed and merged: |
Documentation of python user code deployment and yaml job definition.
Note: This docs will be valid after UCD is released in Viridian. Also the base image name is not defined yet officially. It should be fixed after it is created.