Fixed
Status Update
No update yet.
Comments
ka...@gmail.com
ka...@gmail.com
Can't COUNT_DISTINCT() over a specific date range!!! This appears to be a common problem! Please fix ASAP!
ak...@google.com
ak...@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.
ak...@google.com
Having the same issue with count distinct when selecting a specific filter
ka...@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.
an...@google.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.
ak...@google.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...
ak...@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.
Description
- Build Number: google/panther_beta/panther:15/AP41.240823.009/12329489:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this?
Bluetooth
Time when bug report was triggered:
Oct 14, 2024 16:01 GMT+02:00
What steps would let us observe this issue?
1. After I updated to v 15 yesterday my Bluetooth in ear JBL headphones have the highest volume. The only way to get normal volume is by restarting the phone. Other BT headset works.
What did you expect to happen?
Headphones to have normal volume
What actually happened?
Highest volume
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
Extreme - device was unusable
Additional comments
My ears get destroyed
Debugging information
Google Play services
com.google.android.gms
Version 243934035 (24.39.34 (260400-683343373))
System App (Updated)
Android System WebView
com.google.android.webview
Version 666808133 (129.0.6668.81)
System App (Updated)
Network operator: 3
SIM operator: 3
Filed by Android Beta Feedback. Version (Updated): 2.45-betterbug.external_20240829_RC01 (DOGFOOD)
To learn more about our feedback process, please visit