You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2021. It is now read-only.
There should be a convenient way to trigger a global re-index for times when the xapit index definition changes. We already have the rake xapit:index task, but that cannot be called alongside the syncing process because of the lock on the writable database.
Perhaps a special XapitChange record could be created which tells the separate process to re-index everything. It would be nice if this re-indexing worked on a separate database file and then swapped it out when it was done.
Now what about XapitChange records which get created during the global re-indexing? These may or may not need to take effect depending on the current progress.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There should be a convenient way to trigger a global re-index for times when the xapit index definition changes. We already have the
rake xapit:index
task, but that cannot be called alongside the syncing process because of the lock on the writable database.Perhaps a special XapitChange record could be created which tells the separate process to re-index everything. It would be nice if this re-indexing worked on a separate database file and then swapped it out when it was done.
Now what about XapitChange records which get created during the global re-indexing? These may or may not need to take effect depending on the current progress.
The text was updated successfully, but these errors were encountered: