-
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
Change to using published solrcloud gem #17
Conversation
… old collections to keep.
lib/authority_browse/solr.rb
Outdated
# @return [Array] Array of old authority browse Solrcloud collection | ||
# strings | ||
def self.list_old_collections(list = S.solrcloud.collections) | ||
def self.list_old_collections(list = S.solrcloud.collections, keep: 3) |
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.
Good idea
lib/authority_browse/solr.rb
Outdated
collections: [collection_name] | ||
} | ||
) | ||
S.solrcloud.create_alias(name: reindex_alias, collection_name: collection_name) |
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.
This and set_production_alias
needs force
Re: |
I'm actually going to add date/timestamp stuff to the SolrCloud::Connection gem and then we can use that. |
Two minor changes:
list_old_collections
to specify how many you want to keep and wrote a test for itTwo questions:
Was there a reason for that?
out in the same order). Makes we wonder if we should use YYYY-mm-dd-hhmmss and find everything before
now
except the last N (i.e., turnnow
into aYYYY-mm-dd-hhmmss
string and use that for the comparison).