-
Notifications
You must be signed in to change notification settings - Fork 490
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'develop' into 7662-solrconfig
- Loading branch information
Showing
40 changed files
with
596 additions
and
321 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
# Providing S3 Storage Credentials via MicroProfile Config | ||
|
||
With this release, you may use two new options to pass an access key identifier and a secret access key for S3-based | ||
storage definitions without creating the files used by the AWS CLI tools (`~/.aws/config` & `~/.aws/credentials`). | ||
|
||
This has been added to ease setups using containers (Docker, Podman, Kubernetes, OpenShift) or testing and developing | ||
installations. Find added [documentation and a word of warning in the installation guide](https://guides.dataverse.org/en/latest/installation/config.html#s3-mpconfig). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
Ingest and file upload messaging improvements | ||
|
||
On the pages for adding files on create or edit | ||
|
||
- Explain that all types are supported, link to tabular ingest guides | ||
- Show max files per upload #7227 | ||
- Show global tabular ingest limit | ||
- Show per format tabular ingest limits | ||
- Move messaging from blue info block to regular text. | ||
|
||
Failed ingest messaging | ||
|
||
- Calm blue message that files are available in original format only | ||
- Click for a popup about ingest and specifics of why ingest failed | ||
|
||
Email notification for ingest success | ||
|
||
- Link to tabular ingest guides | ||
- Don't show the files that were just ingested | ||
|
||
Email notification for ingest failure | ||
|
||
- Link to tabular ingest guides | ||
- Say "incomplete" instead of "error" | ||
|
||
Email notification for mix of ingest success and failure | ||
|
||
- Looks just like the email for failure, no mention of files that had success | ||
|
||
In-app notification for ingest success | ||
|
||
- Reworded and links to guides | ||
|
||
In-app notification for ingest failure | ||
|
||
- Reworded and links to guides |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
## Notes for Dataverse Installation Administrators | ||
|
||
### PostgreSQL Version 10+ Required | ||
|
||
If you are still using PostgreSQL 9.X, now is the time to upgrade. PostgreSQL is now EOL (no longer supported, as of January 2022), and the Flyway library in the next release of the Dataverse Software will no longer work with versions prior to 10. | ||
|
||
The Dataverse Software has been tested with PostgreSQL versions up to 13. The current stable version 13.5 is recommended. If that's not an option for reasons specific to your installation (for example, if PostgreSQL 13.5 is not available for the OS distribution you are using), any 10+ version should work. | ||
|
||
See the upgrade section for more information. | ||
|
||
|
||
### PostgreSQL Upgrade (for the "Upgrade Instructions" section) | ||
|
||
The tested and recommended way of upgrading an existing database is as follows: | ||
|
||
- Export your current database with ``pg_dumpall``; | ||
- Install the new version of PostgreSQL; (make sure it's running on the same port, so that no changes are needed in the Payara configuration) | ||
- Re-import the database with ``psql``, as the user ``postgres``. | ||
|
||
It is strongly recommended to use the versions of the ``pg_dumpall`` and ``psql`` from the old and new versions of PostgreSQL, respectively. For example, the commands below were used to migrate a database running under PostgreSQL 9.6 to 13.5. Adjust the versions and the path names to match your environment. | ||
|
||
Back up/export: | ||
|
||
``/usr/pgsql-9.6/bin/pg_dumpall -U postgres > /tmp/backup.sql`` | ||
|
||
Restore/import: | ||
|
||
``/usr/pgsql-13/bin/psql -U postgres -f /tmp/backup.sql`` | ||
|
||
When upgrading the production database here at Harvard IQSS we were able to go from version 9.6 all the way to 13.3 without any issues. | ||
|
||
You may want to try these backup and restore steps on a test server, to get an accurate estimate of how much downtime to expect with the final production upgrade. That of course will depend on the size of your database. | ||
|
||
Consult the PostgreSQL upgrade documentation for more information, for example <https://www.postgresql.org/docs/13/upgrading.html#UPGRADING-VIA-PGDUMPALL>. | ||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.