-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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: fix html nits #13835
docs: fix html nits #13835
Conversation
(cherry picked from commit 882e12a)
Hey @317brian I have #13747 failing on a static CI check for something that looks appropriate for this PR and I'm guessing it will fail for you as well?
Although to be fair I have no idea what its upset about? Seems to be complaining about this line |
Yeah, someone else was running into this earlier. It passes spellcheck locally, but for some reason the GHA doesn't like the position of the comma. It wants it outside of the `, which is technically correct but looks odd in the rendered output. |
@@ -53,7 +53,7 @@ Edit the new file as follows: | |||
4. Move the `format` definition from `parser.parseSpec` to an `inputFormat` definition in `ioConfig`. | |||
5. Delete the `parser` definition. | |||
6. Save the file. | |||
<br>You can check the format of your new ingestion file against the [migrated example](#example-ingestion-spec-after-migration) below. | |||
<br />You can check the format of your new ingestion file against the [migrated example](#example-ingestion-spec-after-migration) below. |
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.
Break here isn't really needed. Reads better without it.
docs/ingestion/ingestion-spec.md
Outdated
@@ -477,7 +477,7 @@ The `indexSpec` object can include the following properties: | |||
|-----|-----------|-------| | |||
|bitmap|Compression format for bitmap indexes. Should be a JSON object with `type` set to `roaring` or `concise`. For type `roaring`, the boolean property `compressRunOnSerialization` (defaults to true) controls whether or not run-length encoding will be used when it is determined to be more space-efficient.|`{"type": "roaring"}`| | |||
|dimensionCompression|Compression format for dimension columns. Options are `lz4`, `lzf`, `zstd`, or `uncompressed`.|`lz4`| | |||
|stringDictionaryEncoding|Encoding format for STRING value dictionaries used by STRING and COMPLEX<json> columns. <br>Example to enable front coding: `{"type":"frontCoded", "bucketSize": 4}`<br>`bucketSize` is the number of values to place in a bucket to perform delta encoding. Must be a power of 2, maximum is 128. Defaults to 4.<br>See [Front coding](#front-coding) for more information.|`{"type":"utf8"}`| | |||
|stringDictionaryEncoding|Encoding format for STRING value dictionaries used by STRING and COMPLEX<json> columns. <br />Example to enable front coding: `{"type":"frontCoded", "bucketSize": 4}`<br />`bucketSize` is the number of values to place in a bucket to perform delta encoding. Must be a power of 2, maximum is 128. Defaults to 4.<br />See [Front coding](#front-coding) for more information.|`{"type":"utf8"}`| |
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.
Breaks here do seem to be needed: at least the VS Code preview gets confused with newlines within a table.
Elsewhere in this table we use two breaks to create a clear separation between paragraphs. Should we do that here as well for consistency? The resulting text looks better.
<br>You can use this property to load segments with future start and end dates, where "future" is relative to the time when the Coordinator evaluates data against the rule. Defaults to `true`. | ||
<br />- the segment interval overlaps the rule interval, or | ||
<br />- the segment interval starts any time after the rule interval starts. | ||
<br />You can use this property to load segments with future start and end dates, where "future" is relative to the time when the Coordinator evaluates data against the rule. Defaults to `true`. |
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.
At the cost of extra per-line spacing, you can replace the <br />
above with two spaces and get the same effect in a more Markdown-ish way. Here and below.
@@ -45,7 +45,7 @@ Before you follow the steps in this tutorial, download Druid as described in the | |||
``` | |||
2. If you're already running Kafka on the machine you're using for this tutorial, delete or rename the `kafka-logs` directory in `/tmp`. | |||
|
|||
> Druid and Kafka both rely on [Apache ZooKeeper](https://zookeeper.apache.org/) to coordinate and manage services. Because Druid is already running, Kafka attaches to the Druid ZooKeeper instance when it starts up.<br> | |||
> Druid and Kafka both rely on [Apache ZooKeeper](https://zookeeper.apache.org/) to coordinate and manage services. Because Druid is already running, Kafka attaches to the Druid ZooKeeper instance when it starts up.<br /> |
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.
This reads better as:
> Druid and Kafka both rely on ...
>
> In a production environment ...
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.
No need for the <br/>
, but no harm either.
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
@@ -45,7 +45,7 @@ Before you follow the steps in this tutorial, download Druid as described in the | |||
``` | |||
2. If you're already running Kafka on the machine you're using for this tutorial, delete or rename the `kafka-logs` directory in `/tmp`. | |||
|
|||
> Druid and Kafka both rely on [Apache ZooKeeper](https://zookeeper.apache.org/) to coordinate and manage services. Because Druid is already running, Kafka attaches to the Druid ZooKeeper instance when it starts up.<br> | |||
> Druid and Kafka both rely on [Apache ZooKeeper](https://zookeeper.apache.org/) to coordinate and manage services. Because Druid is already running, Kafka attaches to the Druid ZooKeeper instance when it starts up.<br /> |
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.
No need for the <br/>
, but no harm either.
The step in CI that's failing is the license check
It's unlikely to be caused by this PR since this PR only touches files in |
Description
Really minor fixes like closing the
<br />
tag in preparation for Docusaurus2, which doesn't like it when they're not closed.This PR has: