-
Notifications
You must be signed in to change notification settings - Fork 2.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
Reviewing Datasource guide #32802
Reviewing Datasource guide #32802
Conversation
🙈 The PR is closed and the preview is expired. |
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, here are my two cents.
I'm afraid a lot of it feels like nitpicking over the form rather than the content, but I guess that cannot be avoided if the goal is to improve the form :)
9930174
to
8527799
Compare
@yrodiere I patched the For more information sentences and drop the confusing lines on 610-611. Patched and rebased. Update JDBC table and create another one (for Reactive drivers). Will move that into the new Reference section when all I did will be approved. |
8527799
to
5df4667
Compare
80f322a
to
e8c0121
Compare
fe8ad63
to
dda9559
Compare
30530c2
to
07b1049
Compare
Hello @michelle-purcell ! Please, I applied feedback from my SMEs, and already did a first iteration of general review. Could I ask you for a little bit of your magic? :) |
07b1049
to
efd267e
Compare
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.
@MichalMaler - A super start to recomposing 🦾 LGTM just some minor comments for minimalism and for Quarkus style consistency. See my comments above. Thanks :-)
f956a53
to
91f68f1
Compare
91f68f1
to
71b38dc
Compare
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've submitted some minor nitpicks, things I suspect I'd find confusing as a newcomer.
I hope they can be addressed, but feel free to dismiss them if it would take too long or of it's not a good time - I would prefer iterations over blocking this for too long.
|
||
When using one of the built-in datasource kinds, the JDBC and Reactive drivers are resolved automatically to match the values from these tables. | ||
|
||
.Database kind to JDBC driver mapping |
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.
Let's rework the title as "Database platform kind to JDBC driver mapping" ?
So it better expressed what we mean by kind, and make it findable too
@@ -3,62 +3,61 @@ This guide is maintained in the main Quarkus repository | |||
and pull requests should be submitted there: | |||
https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc | |||
//// | |||
= Datasources | |||
[id="datasources"] | |||
= Configure datasources in Quarkus |
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.
@MichalMaler /@Sanne - The Vale linter spelling warning on the term datasources
is creating noise in this PR.
As this is an accepted term in Quarkus, I think we should add an exception to this rule. WDYT?
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.
Yeah, I agree :)
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.
Well. This is the discussion. We confuse "data source" (noun) with "datasource" (the code artifact.
Technically speaking, the title should be "Configure data sources in Quarkus". Depends on how semantically correct we want to be. Quarkus has habitually used the two forms interchangably, but that doesn't mean it is correct. ;)
(the id can be datasources, or should be datasource if we want to stick with file conventions... ).
@Sanne Thank you so much, Sanne for your review! Applied some of your comments and will continue with the rest first thing on Monday. |
42aa705
to
2cdc106
Compare
Signed-off-by: Michal Maléř <[email protected]> Applying suggestions form an SME review-1 Signed-off-by: Michal Maléř <[email protected]> Applying suggestions form an SME review-2 Signed-off-by: Michal Maléř <[email protected]> Applying suggestions form an SME review-3 Signed-off-by: Michal Maléř <[email protected]> Apply suggestions from code review Co-authored-by: Yoann Rodière <[email protected]> Tables revamped Signed-off-by: Michal Maléř <[email protected]> FIxes Signed-off-by: Michal Maléř <[email protected]> Fixes Signed-off-by: Michal Maléř <[email protected]> Fixes Signed-off-by: Michal Maléř <[email protected]> Fixes Signed-off-by: Michal Maléř <[email protected]> Fixes Signed-off-by: Michal Maléř <[email protected]> Fixes Signed-off-by: Michal Maléř <[email protected]> Fixes Signed-off-by: Michal Maléř <[email protected]> Fixes Signed-off-by: Michal Maléř <[email protected]> Apply suggestions from code review Co-authored-by: Michelle Purcell <[email protected]> Erin fixes1 Signed-off-by: Michal Maléř <[email protected]> Erin fixes2 Signed-off-by: Michal Maléř <[email protected]> Fixes Signed-off-by: Michal Maléř <[email protected]> Fixes2 Signed-off-by: Michal Maléř <[email protected]> Fixes2 Signed-off-by: Michal Maléř <[email protected]>
2cdc106
to
8f3ae4d
Compare
Hello everyone! This guide has received a humongous review and underwent numerous updates, incorporating suggestions from @jmartisk , @yrodiere , @Sanne , @michelle-purcell , and @ebullient . I propose merging this iteration and scheduling a meeting with someone knowledgeable about Datasource to discuss the next iteration. Taking a more team-oriented approach will allow us to further enhance the content with professional input. Without additional support from you, seasoned developers, there is limited progress I can make on this content that needs to be published in RHBOQ too. Let's move forward together! :) Regarding the future rework to Diataxes templates, would you @ebullient help me with some planning? I would like to have your experienced opinion before taking this further too. |
@MichalMaler agreed! Better to have multiple iterations. Merging... Please remember there were some pending suggestions (which we seem we had already agreed on?) which haven't been applied yet. |
@Sanne <1> If you only have a single Reactive driver extension or are running tests and only have a single test-scoped Reactive driver extension added, then this is optional. Proposing: The rest was applied or tested with @jmartisk and found correct. Or is there anything else overlooked? I was closing the suggestions as I applied them to a commit. |
@MichalMaler np, it gets confusing when it's this large. There's these pending:
And +1 for your proposal, just send other PRs so we can resume nitpicking :) |
Oh, they were both updated :) The suggestion you adressed was a comment, not a suggestion, so I could not close/solve it when done :) And I addressed Erin's proposal to change the main heading too :) It says Next smaller PR coming soon :) @Sanne |
* Derby cannot be embedded into the application in native mode, and only remote connection is supported. | ||
[IMPORTANT] | ||
==== | ||
Embedding H2 within your native image is not recommended. |
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.
Is there any more detail on why this is not recommended? See #6320 (comment)
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.
As far as I know, just because of uncertainty regarding bugs, feature coverage, performance. It started out as something experimental and didn't change much since then.
We haven't had many bug reports either, so you can interpret that any way you like: either nobody uses H2 in native images, or it works fine.
I am proposing a complete review of the Datasource guide, which act as the first iteration of the refactorization.
In the next iterations, the Datasource content will be split into 3 Diataxes module templates.