Skip to content

Conversation

parameswaranvv
Copy link
Contributor

For issue: #20688, Minor change to description of Hikari Datasource properties in documentation

Fixes gh-20688

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Mar 30, 2020
Copy link
Member

@wilkinsona wilkinsona left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks very much for the pull request. I've suggested a small refinement. Could you please take a look and, if you agree, update things accordingly?

@wilkinsona wilkinsona added the status: waiting-for-feedback We need additional information before we can continue label Mar 30, 2020
@wilkinsona wilkinsona added type: documentation A documentation update and removed status: waiting-for-feedback We need additional information before we can continue status: waiting-for-triage An issue we've not yet triaged labels Mar 30, 2020
@wilkinsona wilkinsona added this to the 2.2.x milestone Mar 30, 2020
@wilkinsona wilkinsona changed the title Issue #20688 - Documentation update for Hikari Datasource properties Clarify that spring.datasource.hikari.* properties are bound to a HikariDataSource instance Mar 30, 2020
@wilkinsona wilkinsona self-assigned this Mar 31, 2020
@wilkinsona wilkinsona changed the title Clarify that spring.datasource.hikari.* properties are bound to a HikariDataSource instance Clarify the type to which connection pool specific spring.datasource properties are bound Mar 31, 2020
@wilkinsona wilkinsona changed the title Clarify the type to which connection pool specific spring.datasource properties are bound Clarify the type to which connection-pool-specific spring.datasource properties are bound Mar 31, 2020
@wilkinsona
Copy link
Member

Thanks very much for making your first contribution to Spring Boot, @parameswaranvv. In reviewing the changes, I realised that they were applicable to Commons DBCP2 and Tomcat JDBC as well. I made similar updates for both of those in a polishing commit. I also had to drop the use of backticks around the class name as the column in the table was rendering them as-is. Apologies for the bad suggestion there.

@wilkinsona wilkinsona modified the milestones: 2.2.x, 2.2.7 Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation A documentation update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify that spring.datasource.hikari.* properties are bound to a HikariDataSource instance
3 participants