miike
miike
We've noticed some significant performance improvements when using AZ64 compression (particularly on timestamps). The difference in terms of disk space is minimal (-2% to 2%) we've found but the performance...
It would be interesting to allow for the trackers - primarily the Javascript tracker to have a configuration option of turning on sampling. Initially the implementation could be quite minimal...
There's a spelling error in a few of the bad rows schemas - the error exists in the schemas themselves but the upstream components have the correct spelling. I'm not...
This change corrects the spelling of 'alpha' for enum sets.
Currently [NetworkInfo](https://developer.android.com/reference/android/net/NetworkInfo) is being used to capture networkType which has been deprecated in API level 29. I think it is worth considering switching to [NetworkCapabilities](https://developer.android.com/reference/android/net/ConnectivityManager#getNetworkCapabilities(android.net.Network)) (supported in >= API 21)...
By replacing some of the current transaction FLOAT types with NUMERIC we avoid any floating point arithmetic issues that we can run into if using BigQuerys FLOAT64.
Given that BigQuery now has some geography support does it make sense to convert the latitude / longitude columns to a single `GEOGRAPHY` column of type ST_GEOGPOINT?
It's early days for the SUPER type (preview mode, https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-redshift-announces-support-native-json-semi-structured-data-processing/) but I think it may possibly be a good fit for semi-structured data that is currently shredded into individual tables...
It'd be nice to be able to copy a dataLayer event (or JSON example) and generate a schema from it. [Quicktype](https://app.quicktype.io/) seems to do a reasonably good job of this...
Similar to the network debug panel it would be nice to have the ability to 'Copy As' an event. Initially we could keep this simple (cURL support) by right clicking...