1,013 karma · joined April 5, 2013
If you come from Dataswarm/Airflow then you can use JINJA for the templating, UPSERTS are better when you want to save space by not keeping the same data for each snapshot you take day after day (on multi terabyte tables the space savings are considerable).
More topics that are usually prevalent in distributed systems: - Join order - Type optimization for smaller tables (ones you can fit in memory to do broadcast joins) - Field codification for extra compression/smaller intermediate shuffles when processing data. - Field sorting for extra compression - Caching tables that participate in several parts of the process. - Rolling accumulating pre-aggregates for multi-day processing - T-Digest for performant aggs / cubes - HLL for performant aggs - etc
then telemetry can actually be beneficial to keep improving your product and features.
I like that there is a light signaling the glasses are capturing photo/video, although it might not be noticeable in some cases, just like other devices
Cool to see the pictures/videos don't go directly to FB.
Thank you
This is exactly how it works in Chile, you pretty much check the numbers and make sure they match with your figures and done. For free.
- How do you make sure the users are not writing badly optimized tables/pipelines that end up consuming too many resources.
- How do you facilitate data discoverability so they don't end up creating a new table where 90%+ of the data is already present in another already existing one?
- How do you make sure they are mindful with the way the model the tables such there are not too many files due to bad partition/bucketing, compression is leveraged and good datatypes are picked?