[SPARK-46775][DOCS] Fix formatting of Kinesis docs #44802
Closed
Conversation
This file contains 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
nchammas
commented
Jan 19, 2024
| .build(); | ||
| ``` | ||
|
|
||
| See the [API docs](api/java/org/apache/spark/streaming/kinesis/package-summary.html) |
There was a problem hiding this comment.
The old link was broken, but I cannot find a Java API doc for KinesisInputDStream so I just linked to the package summary.
Maybe @HeartSaVioR knows what's going on here?
| .build() | ||
| ``` | ||
|
|
||
| See the [API docs](api/scala/org/apache/spark/streaming/kinesis/KinesisInputDStream$.html) |
There was a problem hiding this comment.
The old link was also broken here. It just needed the $ at the end.
nchammas
changed the title
HyukjinKwon
approved these changes
Jan 22, 2024
|
Merged to master. |
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.
What changes were proposed in this pull request?
Why are the changes needed?
This makes the docs a bit easier to read and edit.
Does this PR introduce any user-facing change?
Yes, it changes the formatting of this documentation.
How was this patch tested?
I built the docs and manually reviewed them.
Was this patch authored or co-authored using generative AI tooling?
No.