Skip to content
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

[Content Bug] Delete_job error in the User defined-actions how-to guide #112

Closed
lucieva opened this issue Jun 7, 2021 · 0 comments
Closed
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@lucieva
Copy link

lucieva commented Jun 7, 2021

Describe the bug

The link to "delete_job" gives a not found error.

What do the docs say now?

https://docs.timescale.com/api/latest/actions-and-automation/delete_job/

What should the docs say?

https://docs.timescale.com/api/latest/actions/delete_job/

Page affected

https://docs.timescale.com/timescaledb/latest/how-to-guides/user-defined-actions/alter-and-delete/# Version affected

Version affected

latest

Subject matter expert (SME)

[If known, who is a good person to ask about this topic]

Screenshots

image

Any further info

[Anything else you want to add, or further links]

@lucieva lucieva added bug Something isn't working documentation Improvements or additions to documentation labels Jun 7, 2021
Loquacity added a commit that referenced this issue Jun 10, 2021
* Fixes to Actions documentation based on GitHub issues #110, #111, #112, #113, #114

* additional link fixes

* One more

Co-authored-by: Lana Brindley <github@lanabrindley.com>
konskov added a commit that referenced this issue Dec 12, 2022
Timescaledb-tune had not been updated so there was a
discrepance between the default value set by timescaledb-tune(8) and the
default value of the GUC set in timescaledb(16). Updated tsdb-tune in
timescale/timescaledb-tune/#112 to agree with the default timescaledb value
so also updating the documentation for this change.
Loquacity added a commit that referenced this issue Jan 6, 2023
Timescaledb-tune had not been updated so there was a
discrepance between the default value set by timescaledb-tune(8) and the
default value of the GUC set in timescaledb(16). Updated tsdb-tune in
timescale/timescaledb-tune/#112 to agree with the default timescaledb value
so also updating the documentation for this change.

Co-authored-by: Lana Brindley <github@lanabrindley.com>
Co-authored-by: Rajakavitha Kodhandapani <krajakavitha@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants