Add properties, requirements, and best practices from FTE blog#12231
Add properties, requirements, and best practices from FTE blog#12231arhimondr merged 1 commit intotrinodb:masterfrom
Conversation
There was a problem hiding this comment.
Should we use code highlighting for the error message?
There was a problem hiding this comment.
I worry it'll cause issues with SEO, which is the whole reason to have the full error text here.
There was a problem hiding this comment.
This is the default, right?
There was a problem hiding this comment.
If the docs are correct, then yes. Still worth calling out I think, because it's a property that a reader might not associate with FTE and have configured differently.
There was a problem hiding this comment.
I'm thinking about introducing a dedicated property for fault tolerant execution with an appropriate default. The discussion is happening here: #12228 (comment)
jhlodin
force-pushed
the
jl/fte-blog-improvements
branch
from
4696714 to
8b5bf2b
Compare
jhlodin
force-pushed
the
jl/fte-blog-improvements
branch
from
8b5bf2b to
0b1db37
Compare
|
Added the new property from #12263 to this PR. @arhimondr |
|
Could we this merged with the code changes @arhimondr ? |
4 participants
Description
Add new information gleaned from the Tardigrade blog post PR (trinodb/trino.io#287) to the documentation
Improvement
Documentation
Add new information to the fault-tolerant execution and query management properties documentation
Related issues, pull requests, and links
Incorporates information from trinodb/trino.io#287
Documentation
( ) No documentation is needed.
(x) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(x) No release notes entries required.
( ) Release notes entries required with the following suggested text: