-
Notifications
You must be signed in to change notification settings - Fork 286
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
InfluxDB OSS v1.11.7 #5648
InfluxDB OSS v1.11.7 #5648
Conversation
sanderson
commented
Oct 16, 2024
- InfluxDB OSS v1.11.7 release notes and accompanying documentation.
- Adding missing updates to InfluxDB Enterprise documentation.
- Rebased/mergeable
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.
I focused primarily on the changelog to make sure we mentioned the security fixes. I have a few comments inline.
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.
Approving the parts I reviewed (changelog for security).
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
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.
Thanks for doing all this! I have several small suggestions and fixes.
Co-authored-by: Jason Stirnaman <[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.
A question/suggestion about the command options formatting, but otherwise LGTM
@@ -139,6 +142,31 @@ $ influx_inspect buildtsi -database mydb -datadir ~/.influxdb/data -waldir ~/.in | |||
$ influx_inspect buildtsi -database stress -shard 1 -datadir ~/.influxdb/data -waldir ~/.influxdb/wal | |||
``` | |||
|
|||
### `check-schema` |
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.
- Shouldn't all
options
be optional arguments? - I find the brackets in the headings confusing--I had to scroll up to the previous section to find "Optional arguments are in brackets."--if we need the brackets, then I think we need the explanation.
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.
Yes, this was a convention established long ago in the 1.x CLI docs that I've always hated. At one point, I updated the InfluxDB Enterprise CLI docs to correct for this. I just never went back and updated this doc and didn't want to hang this PR up on correcting that convention. But I agree. It's not good.
While we're talking about it, there are two conventions that have always bugged me in the 1.x docs:
- The bracketed optional influx_inspect CLI flags in the 1.x CLI docs. (I updated the v1
influx
andinfluxd
docs to use our "new" CLI doc conventions, but notinflux_inspect
) - The configuration setting headings that include the default values in the headings
Because they're headings and many of these are referenced in links, these changes have cascading affects that I didn't feel I had time to include in this PR.
…nto influxdb-oss-1.11.7