hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-11-13 09:17:21 +03:00
Code Issues Projects Releases Wiki Activity

docs: add update note for large event/cron logs

Browse Source 
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2136
GitOrigin-RevId: a6c6185d1c093151757d2c0632aef07ca4c38209
This commit is contained in:
Rikin Kachhia 2021-11-19 15:05:47 +05:30 committed by hasura-bot
parent 2b459ed125
commit b6cb186cfd
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/graphql/cloud/projects/move-project-v2.rst
View File

@ -27,7 +27,8 @@ projects to ``v2.0`` by following this guide.
In case you happen to have a large number of past cron and event trigger logs in your database, this might slow down the update
to v2 and might even cause DB errors in certain scenarios.
**It is highly recommended to clean up past cron and event trigger logs data from the database before attempting the update**.
**It is highly recommended to clean up past cron and event trigger logs data from the database before attempting the update if you
have a lot of historical data.**
You can take a dump of this data before cleaning up if you wish to keep the log history.

5
docs/graphql/core/guides/upgrade-hasura-v2.rst
View File

@ -190,7 +190,8 @@ assumed to belong to it.
In case you happen to have a large number of past cron and event trigger logs in your database, this might slow down the update
to v2 and might even cause unexpected errors in certain scenarios.
**It is highly recommended to clean up past cron and event trigger logs data from the database before attempting the update**.
**It is highly recommended to clean up past cron and event trigger logs data from the database before attempting the update if you
have a lot of historical data.**
You can take a dump of this data before cleaning up if you wish to keep the log history. This data can be restored back into the DB if
required post the update.
@ -265,4 +266,4 @@ docker image version and using the :ref:`downgrade command <downgrade_hge>` to r
.. note::
You can downgrade a Hasura v2 instance to Hasura v1 only if there is only one database connected to it.
You can downgrade a Hasura v2 instance to Hasura v1 only if there is only one database connected to it.