Obsolete
Status Update
No update yet.
Comments
va...@gmail.com
va...@gmail.com
Can't COUNT_DISTINCT() over a specific date range!!! This appears to be a common problem! Please fix ASAP!
an...@google.com
an...@google.com
Instead of counting unique values in a specified column COUNT_DISCTINCT counts rows in a database (on a view, not a table, to be more specific)... It works as expected with spreadsheets.
ra...@gmail.com
Having the same issue with count distinct when selecting a specific filter
jo...@gmail.com
From my side, I'm using Postgres Database (All good in Postgres doing the same grouping-unique, so no issues in DB or in Data).
If no values are selected in Filter Control widget the COUNT_DISTINCT is working as expected as it's getting Unique values for the entire dataset, but when I put a value in Filter Control, COUNT_DISTINCT is generating a wrong value.
If no values are selected in Filter Control widget the COUNT_DISTINCT is working as expected as it's getting Unique values for the entire dataset, but when I put a value in Filter Control, COUNT_DISTINCT is generating a wrong value.
ai...@gmail.com
I've run into the same issue. I'm connected to Postgres. When I apply a date filter to any metrics that use COUNT DISTINCT, the results wind up being COUNTs.
br...@gmail.com
I can't believe that Google has left this bug unresolved for months, this is a joke. Any time we apply date filtering, and try to utilise count distinct aggregation, when we apply further filtering through other dimensions, the metrics become extremely overstated.
Please sort this out Google, we will have to move to a different tool as this is fundamental functionality...
Please sort this out Google, we will have to move to a different tool as this is fundamental functionality...
ad...@google.com
My read on this is that Google doesn't care about Postgres/Redshift support for GDS, and that anyone not on BigQuery should choose a different BI tool. It's really unfortunate because GDS seemed to have a lot of potential.
ad...@google.com
We're using Big Query and have similar issue, don't know how long we have
to wait to get this resolved.
On Tue, Feb 4, 2020 at 1:02 PM <buganizer-system@google.com> wrote:
to wait to get this resolved.
On Tue, Feb 4, 2020 at 1:02 PM <buganizer-system@google.com> wrote:
jo...@gmail.com
Yeah, I don't think this is connector specific. It more so seems like a bug in how Data Studio handles count distinct aggregation when applying a date range and in conjunction with filtering with other dimensions. I created another thread for this here: https://issuetracker.google.com/issues/148813902
Feel free to jump in on it and comment as well, this bug is affecting us massively here.
Feel free to jump in on it and comment as well, this bug is affecting us massively here.
ad...@google.com
On our side it's probably working with a view vs actual table. Funny enough same data with the same filters displays in expected number of rows (so it can distinguish between unique entries properly (same string)).
jo...@gmail.com
Interesting. I am using Postgres and I gave your idea a shot, but a view and a table result in the same bug. However, I also tested to load the exact same data source onto Google Sheets and then load it onto Data Studio and the problem was resolved. So I was wrong^^ it IS connector specific. I guess the guy above^ is probably right. I'm pretty sure Google is aware of this but doubt they will ever fix it.
Best case if any one stumbles upon this 1) Either use a proxy like GSheets to load your data on there first if you are experiencing this bug with MySQL or Postgres or whatever other engine, or 2) Switch to a different BI tool!
Best case if any one stumbles upon this 1) Either use a proxy like GSheets to load your data on there first if you are experiencing this bug with MySQL or Postgres or whatever other engine, or 2) Switch to a different BI tool!
ni...@googlemail.com
Using Redshift with the Postgresql connector. When I render the individual values as a table, everything is correct, but when I render a COUNT DISTINCT in a score card I get incorrect numbers similar to what has been described above. We've really liked Data Studio so far as a BI Tool but it's a serious bullet if it can't do such a basic counting function correctly. The worst thing to present in a business report is data that is obviously wrong.
jo...@gmail.com
Same problem here. Count_distinct(column) fails when multiple values of a filter is applied.
Very Critical for us.
Very Critical for us.
jo...@gmail.com
It's incredible given how debilitating this is, how long this bug has existed 😢
kb...@gmail.com
Same problem on Postgres, please get this fixed, it GROUP BY on the date range dimension field so it's unable to COUNT DISTINCT properly
ko...@gmail.com
I've ran into this issue before using a Postgres connector but I've ran into it again now using the file upload (.csv) connector too. Interestingly, the Data Studio Explorer shows the correct values (using same config)!
ad...@google.com
I'm having the same issue, reading from a CSV and unable to count_distinct() a text field. Somehow this is fixed if I blend the data
jo...@gmail.com
Same here. Postgres connector. count_distinct() returns the value as if it were grouped by day and then summed, rather than a true distinct count for the duration of the date range selected
ad...@google.com
Same issue here...csv file, when a data range is selected, them returns incorrect value
an...@google.com
same here. Mysql connector. Data range filter + count distinct >> wrong value
va...@gmail.com
Same issue. We solved by combining the data with itself, but it's a very dirty solution. Wait for a real fix !!
I also try using directly a calculated field with COUNT_DISTINCT() but it gave the same wrong result.
I also try using directly a calculated field with COUNT_DISTINCT() but it gave the same wrong result.
ad...@google.com
This has nothing to do with connetors or anything.
The problem is probably that COUNT_DISTINCT get's executed before the filter and afterwards the filtered values get aggregated together (mostly summed). It's a real Deal breaker ...
The problem is probably that COUNT_DISTINCT get's executed before the filter and afterwards the filtered values get aggregated together (mostly summed). It's a real Deal breaker ...
ad...@google.com
Same issue here, from postgres connector. I would really appreciate if some time was allocated to fix this issue.
va...@gmail.com
Same here. Postgres connector. count_distinct() returns the value as if it were grouped by day and then summed, rather than a true distinct count for the duration of the date range selected
ad...@google.com
It fails when dimension is a date and metric is CTD. I use mysql connector and experiencing same issue.
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of issue is this? Other issue
When did this happen?
20 мая 2024 г. 00:23 GMT+07:00
What steps would let us observe this issue?
1. run any game mode with real players. FPS drops during battle
What did you expect to happen?
before the update there were stable 60 fps
What actually happened?
under any load fps drops to 15-30
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
High
Additional comments
the game works terribly
Related apps
Wild Rift
com.riotgames.league.wildrift
Version 789564 (5.1.0.7895)
Not system app
Debugging information
Сервисы Google Play
com.google.android.gms
Version 241616038 (24.16.16 (190400-629452829))
System App (Updated)
Android System WebView
com.google.android.webview
Version 636758232 (124.0.6367.82)
System App (Updated)
Network operator: MTS RUS
SIM operator: MTS RUS
Filed by Android Beta Feedback. Version (Bundled): 2.25-betterbug.external_20220328_RC02
To learn more about our feedback process, please visit