Skip to content
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

Support limit for archive policies #65

Open
jmfee-usgs opened this issue Dec 6, 2017 · 2 comments
Open

Support limit for archive policies #65

jmfee-usgs opened this issue Dec 6, 2017 · 2 comments

Comments

@jmfee-usgs
Copy link
Contributor

Policies currently query the index for matching products/events to be archived.
If policy is broad, query may take a while and block ongoing indexing.

@jmfee-usgs jmfee-usgs added this to the v2.2.0 milestone Jul 31, 2019
@Capprin
Copy link
Contributor

Capprin commented Aug 5, 2019

Archive policies are sections of configuration, and are run by the indexer. Because archive queries are sometimes large (and block processing of other products), running with a limit will break up the job and open the opportunity to process other products. Take advantage of the limit parameter added to the ProductIndexQuery.

@Capprin
Copy link
Contributor

Capprin commented Aug 5, 2019

Double check that the limit works for event and product tables. (There exists ArchivePolicy for events and ProductArchivePolicy for products).

@jmfee-usgs jmfee-usgs removed this from the v2.2.0 milestone Aug 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants