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

invalidateArchivedReports API can invalidate report data for a particular '&segment=' #8858

Closed
mattab opened this Issue Sep 27, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@mattab
Member

mattab commented Sep 27, 2015

In: https://piwik.org/faq/how-to/faq_155/

A typical API query to invalidate reports is: ?module=API&method=CoreAdminHome.invalidateArchivedReports&idSites=1,3,5&dates=2012-01-01,2011-10-15&token_auth=xyz

It would be useful when managing a Piwik instance, to be able to invalidate report data for a particular segment only. Why? eg. when invalidating data for a very long date range, sometimes we want to invalidate a particular segment data that we care most about, there is no need to have all other report data reprocessed ( sometimes this could take several days to compute).

Steps

  • Implement feature
  • Include regression test
  • Update FAQ to document this new feature
@mattab

This comment has been minimized.

Show comment
Hide comment
@mattab

mattab Oct 13, 2015

Member

Added to FAQ: it is possible to invalidate and re-process a segmented report only, simply add to the URL query the segment parameter: &segment=pageUrl=@example.org/contact

Member

mattab commented Oct 13, 2015

Added to FAQ: it is possible to invalidate and re-process a segmented report only, simply add to the URL query the segment parameter: &segment=pageUrl=@example.org/contact

@mattab mattab changed the title from invalidateArchivedReports API to invalidate report data for a particular segment to invalidateArchivedReports API can invalidate report data for a particular '&segment=' Oct 13, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment