-
Notifications
You must be signed in to change notification settings - Fork 0
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
Allow pomegranate:reindex Rake task to be used in production #533
Labels
Comments
seems like it would be nice to have a task that takes a noid, as well as one that could do an initial index. |
Also, as long as we're updating our indexing Rake tasks, it would be good to have a task that commits the index, since we've disabled commits in our code, and autocommits take a long time. |
hackartisan
added a commit
that referenced
this issue
Sep 14, 2020
instead of `pomegranate:reindex` it's now `reindex:manifest` refs #533
hackartisan
added a commit
that referenced
this issue
Sep 14, 2020
hackartisan
added a commit
that referenced
this issue
Sep 14, 2020
hackartisan
added a commit
that referenced
this issue
Sep 14, 2020
hackartisan
added a commit
that referenced
this issue
Sep 15, 2020
hackartisan
added a commit
that referenced
this issue
Sep 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pomegranate:reindex
task out of thedev.rake
which is only loaded in dev/test environmentsIIIFResource.find_or_initialize_by
instead offind_by
to allow initial indexing with the Rake taskThe text was updated successfully, but these errors were encountered: