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

Evolution Graph displays "no data" if last date has no data #3465

Closed
tsteur opened this issue Oct 21, 2012 · 11 comments
Closed

Evolution Graph displays "no data" if last date has no data #3465

tsteur opened this issue Oct 21, 2012 · 11 comments
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc. c: Performance For when we could improve the performance / speed of Matomo. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone

Comments

@tsteur
Copy link
Member

tsteur commented Oct 21, 2012

I tried to test evolution graph with "period=range". For example from 8th August 2012 to 2nd September 2012. It renders a graph displaying "No data for this graph" if there are no visits/actions on the last day of the period. If I set range from 8th August 2012 to 3rd September 2012, it dispalys the graph. There are actions and visits in August. It seems just to depend whether there are actions/visits on the last day.

When the graph is displayed with message "No data for this graph", the graph is also loading fast. Maybe it just looks at the last day and does no further queries in this case.

Manage this edge case when there is no data. This happens with any period, not only range.

See #3158
and #3158

@mattab
Copy link
Member

mattab commented Nov 24, 2012

xhprof use is related to #3464

@diosmosis
Copy link
Member

In 930ec65: Refs #3465, use bulk tracking in RowEvolution integration test to speed it up.

@diosmosis
Copy link
Member

In 80ac6ac: Refs #3465, remove Piwik_DataTable_Array::metadata and move data to Piwik_DataTable::metadata.

@diosmosis
Copy link
Member

In 900eec1: Refs #3465, fixing build

@julienmoumne
Copy link
Member

duplicate of #3790

@mattab
Copy link
Member

mattab commented Mar 11, 2013

@julienm wrote in #3790:

Since 3013 the Row Evolution API can be called to retrieve the top N label evolutions.

As suggested in 3158#comment:12, when there are less than 5 labels for the requested period, "top up" the labels list by requesting the report for the current year of data.

@diosmosis
Copy link
Member

In 51b7787: Fixes #3465, refactor row evolution code to fix bug where if no labels are specified and last period has no labels, no data is returned. Refactoring also contains optimization for case where no labels are specified.

Notes:

  • Simplified DataTableManipulator and derived classes.
  • Allow LabelFilter to use multiple labels. Can be used by specifying array for label query parameter (ie, label[]=...).
  • Removed getFilteredTableFromLabel function from datatable types and add getEmptyClone to DataTable_Array.
  • Added setIdSite to php tracker PiwikTracker.

@diosmosis
Copy link
Member

In d9ff500: Refs #3465, fix regression in multi row evolution API output where columns w/ value of 0 were not outputted.

@diosmosis
Copy link
Member

In 7a89c65: Refs #3465, make sure labels are associated with correct rows in multi-row evolution after generic filters (ie, Sort) are applied.

@diosmosis
Copy link
Member

In 204cbc0: Refs #3465, fix regression for flattener filter where queued filters were applied on the flattened datatable.

@diosmosis
Copy link
Member

In a8420c0: Refs #3465, fixing build.

@tsteur tsteur added this to the 1.12 - The Great 1.x Backlog milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. c: Performance For when we could improve the performance / speed of Matomo. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

4 participants