-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add description about placeholders of database.properties #1498
Conversation
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! Thank you!
docs/configurations.md
Outdated
@@ -186,6 +186,10 @@ The following are additional configurations available for ScalarDB: | |||
| `scalar.db.default_namespace_name` | The given namespace name will be used by operations that do not already specify a namespace. | | | |||
| `scalar.db.system_namespace_name` | The given namespace name will be used by ScalarDB internally. | `scalardb` | | |||
|
|||
## Use placeholders | |||
|
|||
You can use placeholders in the values, and they are replaced with environment variables (${env:<ENVIRONMENT_VARIABLE_NAME>}) or system properties (${sys:<SYSTEM_PROPERTY_NAME>}). You can also specify default values in placeholders like ${sys:<SYSTEM_PROPERTY_NAME>:-<DEFAULT_VALUE>}. |
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.
environment variables (${env:<ENVIRONMENT_VARIABLE_NAME>})
How about syntax-highlighting it as follows?
environment variables (`${env:<ENVIRONMENT_VARIABLE_NAME>}`)
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.
Ah, I see. Looks good!
I will apply it. Thank you for your suggestion!
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! Thank you!
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 added some suggestions. PTAL!
Co-authored-by: Josh Wong <joshua.wong@scalar-labs.com>
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 left two additional comments on parts that I had mistakenly looked over. Other than that, LGTM. Thank you!🙇🏻♂️
Co-authored-by: Josh Wong <joshua.wong@scalar-labs.com>
docs/configurations.md
Outdated
@@ -258,3 +262,14 @@ scalar.db.contact_points=indirect:<SCALARDB_CLUSTER_CONTACT_POINT> | |||
``` | |||
|
|||
For details about client configurations, see the ScalarDB Cluster [client configurations (redirects to the Enterprise docs site)](https://scalardb.scalar-labs.com/docs/latest/scalardb-cluster/developer-guide-for-scalardb-cluster-with-java-api/#client-configurations). | |||
|
|||
### Configuration example #3 - Placeholder usage |
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 think we can move this example into the ## Placeholder usage
part. I think this Configuration example
section is more like for the actual/real settings. So if this example is only for the placeholder usage, I think we can put it in the ## Placeholder usage
part. What do you think?
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 see. Indeed, this example does not include the actual configuration (minimum configuration) to access the backend DB or ScalarDB Cluster.
I agree with you. I will move this example into the ## Placeholder usage
section. Thank you!
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 updated it in 910c269.
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! Thank you!
Co-authored-by: Josh Wong <joshua.wong@scalar-labs.com> Co-authored-by: Toshihiro Suzuki <brfrn169@gmail.com>
Co-authored-by: Josh Wong <joshua.wong@scalar-labs.com> Co-authored-by: Toshihiro Suzuki <brfrn169@gmail.com>
Co-authored-by: Josh Wong <joshua.wong@scalar-labs.com> Co-authored-by: Toshihiro Suzuki <brfrn169@gmail.com>
Co-authored-by: Josh Wong <joshua.wong@scalar-labs.com> Co-authored-by: Toshihiro Suzuki <brfrn169@gmail.com>
Co-authored-by: Josh Wong <joshua.wong@scalar-labs.com> Co-authored-by: Toshihiro Suzuki <brfrn169@gmail.com>
Description
This PR adds the description about placeholders in the database.properties file.
We added placeholder support in the database.properties file in PR #770.
There is a Javadoc, which describes this feature, but there is no description in Scalar Docs site.
So, I added the description of the placeholder feature in the document.
Please take a look!
Related issues and/or PRs
Changes made
docs/configurations.md
.Checklist
Additional notes (optional)
N/A
Release notes
N/A