Add docs for input and output format and expected behaviors #575
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xiaoyongzhu
requested review from
Yuqing-cat,
blrchen,
edwincheung,
hangfei,
jainr and
jaymo001
xiaoyongzhu
changed the title
blrchen
reviewed
Aug 11, 2022
blrchen
reviewed
Aug 11, 2022
jainr
reviewed
Aug 19, 2022
jainr
previously approved these changes
Aug 19, 2022
jainr
approved these changes
Aug 19, 2022
blrchen
approved these changes
Aug 20, 2022
ahlag
pushed a commit
to ahlag/feathr
that referenced
this pull request
Aug 26, 2022
…i#575) * Create feathr-input-format.md * update docs * Update feathr-input-format.md * address comments * Update feathr-job-configuration.md * Update feathr-input-format.md * Update build-and-push-feathr-registry-docker-image.md * move file to the right hierachy * Update README.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolves #340
How was this PR tested?
Does this PR introduce any user-facing changes?