[MINOR][DOCS] Use proper html tag in markdown #26302
Closed
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
uncleGen
commented
Oct 30, 2019
| By default, Spark has a 1-1 mapping of topicPartitions to Spark partitions consuming from Kafka. | ||
| If you set this option to a value greater than your topicPartitions, Spark will divvy up large | ||
| Kafka partitions to smaller pieces. Please note that this configuration is like a `hint`: the | ||
| number of Spark tasks will be **approximately** `minPartitions`. It can be less or more depending on |
| <tr> | ||
| <td><b>One-time micro-batch</b></td> | ||
| <td> | ||
| The query will execute *only one* micro-batch to process all the available data and then |
|
Test build #112879 has finished for PR 26302 at commit
|
HyukjinKwon
approved these changes
Oct 30, 2019
Member
|
Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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?
This PR fix and use proper html tag in docs
Why are the changes needed?
Fix documentation format error.
Does this PR introduce any user-facing change?
No
How was this patch tested?
N/A