-
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 documentation for the upgrade feature #1311
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! 👍
docs/api-guide.md
Outdated
@@ -250,6 +250,18 @@ You can get table metadata as follows: | |||
TableMetadata tableMetadata = admin.getTableMetadata("ns", "tbl"); | |||
``` | |||
|
|||
### Upgrade the environment to support the latest ScalarDB API | |||
|
|||
You can upgrade the ScalarDB environment to support the latest version of the ScalarDB API. Typically, |
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.
[trivial] Maybe this is a matter of taste, but
you will be requested
"you will need" is a bit clearer?
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 agree; it sounds better. Thanks.
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 applied your suggestion and also updated Java files containing documentation for upgrade
which use the same wording.
a36972b
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.
LTGM! Thank you!
I left a very minor comment.
Please take a look when you have time!
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!
docs/schema-loader.md
Outdated
--upgrade Upgrades the ScalarDB environment to support the latest | ||
version of the ScalarDB API. Typically, you will be | ||
requested, as indicated on the release notes, to run | ||
this command after updating the ScalarDB version of | ||
your application environment. |
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.
--upgrade Upgrades the ScalarDB environment to support the latest | |
version of the ScalarDB API. Typically, you will be | |
requested, as indicated on the release notes, to run | |
this command after updating the ScalarDB version of | |
your application environment. | |
--upgrade Upgrades the ScalarDB environment to support the latest | |
version of the ScalarDB API. Typically, you will need, as indicated in the release notes, to run | |
this command after updating the ScalarDB version that | |
your application environment uses. |
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.
Thank you. This suggestion is similar to #1311 (comment) so I did not apply it.
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 made some changes aside from the word need
in my original suggestion. (Sorry, my other changes in my suggestion were a bit hard to see.)
Please see my new comment/suggestion, which also incorporates @feeblefakie's suggestion.
Co-authored-by: Josh Wong <joshua.wong@scalar-labs.com> Co-authored-by: kota2and3kan <47254383+kota2and3kan@users.noreply.github.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.
Overall, looking good.
I left one suggestion. There are several places that use the same expression, so I also left comments on those. (but I didn't do it for all the places.)
@@ -436,7 +436,7 @@ void importTable(String namespace, String table, Map<String, String> options) | |||
|
|||
/** | |||
* Upgrades the ScalarDB environment to support the latest version of the ScalarDB API. Typically, | |||
* you will be requested, as indicated on the release notes, to run this method after updating the | |||
* you will need, as indicated on the release notes, to run this method after updating the |
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.
* you will need, as indicated on the release notes, to run this method after updating the | |
* as indicated on the release notes, you will need to run this method after updating the |
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.
@Torch3333 I didn't see that the wording in some of the non-.md
files matched the same wording in the .md
files, so I'm making a suggestion here.
My suggestion below (and in my other comments that contain this sentence revises that) addresses @feeblefakie's suggestion and applies other wording that is consistent with my original suggestion.
* you will need, as indicated on the release notes, to run this method after updating the | |
* as indicated in the release notes, you will need to run this method after updating the |
docs/api-guide.md
Outdated
@@ -250,6 +250,16 @@ You can get table metadata as follows: | |||
TableMetadata tableMetadata = admin.getTableMetadata("ns", "tbl"); | |||
``` | |||
|
|||
### Upgrade the environment to support the latest ScalarDB API | |||
|
|||
You can upgrade the ScalarDB environment to support the latest version of the ScalarDB API. Typically, you will need, as indicated in the release notes, to run this method after updating the ScalarDB version that your application environment uses. |
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.
Ditto.
docs/schema-loader.md
Outdated
@@ -92,6 +92,12 @@ Create/Delete schemas in the storage defined in the config file | |||
The replication strategy, must be SimpleStrategy or | |||
NetworkTopologyStrategy (supported in Cassandra) | |||
--ru=<ru> Base resource unit (supported in DynamoDB, Cosmos DB) | |||
--upgrade Upgrades the ScalarDB environment to support the latest | |||
version of the ScalarDB API. Typically, you will | |||
need, as indicated on the release notes, to run |
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.
Ditto.
docs/schema-loader.md
Outdated
@@ -439,6 +445,14 @@ $ java -jar scalardb-schema-loader-<VERSION>.jar --jdbc -j <JDBC_URL> -u <USER> | |||
|
|||
<div class="notice--info">{{ notice--info | markdownify }}</div> | |||
|
|||
### Upgrade the environment to support the latest ScalarDB API | |||
|
|||
You can upgrade the ScalarDB environment to support the latest version of the ScalarDB API. Typically, you will need, as indicated in the release notes, to run this method after updating the ScalarDB version that your application environment uses. |
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.
Ditto.
docs/storage-abstraction.md
Outdated
@@ -405,6 +405,16 @@ You can get table metadata as follows: | |||
TableMetadata tableMetadata = admin.getTableMetadata("ns", "tbl"); | |||
``` | |||
|
|||
### Upgrade the environment to support the latest ScalarDB API | |||
|
|||
You can upgrade the ScalarDB environment to support the latest version of the ScalarDB API. Typically, you will need, as indicated in the release notes, to run this method after updating the ScalarDB version that your application environment uses. |
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.
Ditto.
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.
Made some suggestions mostly in source code files based on a similar sentence in the Markdown files. PTAL!
@@ -436,7 +436,7 @@ void importTable(String namespace, String table, Map<String, String> options) | |||
|
|||
/** | |||
* Upgrades the ScalarDB environment to support the latest version of the ScalarDB API. Typically, | |||
* you will be requested, as indicated on the release notes, to run this method after updating the | |||
* you will need, as indicated on the release notes, to run this method after updating the |
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.
@Torch3333 I didn't see that the wording in some of the non-.md
files matched the same wording in the .md
files, so I'm making a suggestion here.
My suggestion below (and in my other comments that contain this sentence revises that) addresses @feeblefakie's suggestion and applies other wording that is consistent with my original suggestion.
* you will need, as indicated on the release notes, to run this method after updating the | |
* as indicated in the release notes, you will need to run this method after updating the |
docs/schema-loader.md
Outdated
--upgrade Upgrades the ScalarDB environment to support the latest | ||
version of the ScalarDB API. Typically, you will | ||
need, as indicated on the release notes, to run | ||
this command after updating the ScalarDB version of | ||
your application environment. |
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 made some changes aside from the word need
in my original suggestion. (Sorry, my other changes in my suggestion were a bit hard to see.)
I've also included @feeblefakie's suggestion in my suggestion below:
--upgrade Upgrades the ScalarDB environment to support the latest | |
version of the ScalarDB API. Typically, you will | |
need, as indicated on the release notes, to run | |
this command after updating the ScalarDB version of | |
your application environment. | |
--upgrade Upgrades the ScalarDB environment to support the | |
latest version of the ScalarDB API. Typically, as | |
indicated in the release notes, you will need to | |
run this command after updating the ScalarDB | |
version that your application environment uses. |
@@ -436,7 +436,7 @@ void importTable(String namespace, String table, Map<String, String> options) | |||
|
|||
/** | |||
* Upgrades the ScalarDB environment to support the latest version of the ScalarDB API. Typically, | |||
* you will be requested, as indicated on the release notes, to run this method after updating the | |||
* you will need, as indicated on the release notes, to run this method after updating the | |||
* ScalarDB version of your application environment. |
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.
* ScalarDB version of your application environment. | |
* ScalarDB version that your application environment uses. |
* you will need, as indicated on the release notes, to run this method after updating the | ||
* ScalarDB version of your application environment. |
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.
Similar to my previous comment.
* you will need, as indicated on the release notes, to run this method after updating the | |
* ScalarDB version of your application environment. | |
* as indicated in the release notes, you will need to run this method after updating the | |
* ScalarDB version that your application environment uses. |
* you will need, as indicated on the release notes, to run this method after updating the | ||
* ScalarDB version of your application environment. |
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.
Similar to my previous comment.
* you will need, as indicated on the release notes, to run this method after updating the | |
* ScalarDB version of your application environment. | |
* as indicated in the release notes, you will need to run this method after updating the | |
* ScalarDB version that your application environment uses. |
"Upgrades the ScalarDB environment to support the latest version of the ScalarDB API. Typically, you will need, as indicated on the release notes, to run this command after" | ||
+ " updating the ScalarDB version of your application environment.", |
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.
Similar to my previous comment.
"Upgrades the ScalarDB environment to support the latest version of the ScalarDB API. Typically, you will need, as indicated on the release notes, to run this command after" | |
+ " updating the ScalarDB version of your application environment.", | |
"Upgrades the ScalarDB environment to support the latest version of the ScalarDB API. Typically, as indicated in the release notes, you will need to run this command after" | |
+ " updating the ScalarDB version that your application environment uses.", |
2a6d219
to
f4ebd41
Compare
f4ebd41
to
7e5726f
Compare
…_for_upgrade # Conflicts: # docs/api-guide.md # docs/schema-loader.md # docs/storage-abstraction.md
@feeblefakie @josh-wong |
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 left a minor suggestion (an oversight on my part...). Other than that, LGTM! Thank you!
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.
LGTM! Thank you!
Description
Adds documentation for the
upgrade
feature that was added to the Admin API (admin.upgrade(...)
) and Schema Loader (--upgrade
command).Related issues and/or PRs
upgrade()
to Admin API #1204--upgrade
command to Schema Loader #1208Changes made
This adds sections for the upgrade feature to the api-guide, api-abstraction and Schema Loader documentations.
Checklist
Additional notes (optional)
N/A
Release notes
N/A