That looks like a great suggestion, thanks! It looks like we'd need to break out our JSON data into columns (our events table is basically just an event name, time, user id, and then a jsonb column) and rewrite our queries, but it seems more suitable than anything else I've seen so far.
We've been getting good results with some tweaks to our Postgres indexing (partial indexes on event names makes a huge difference) and that'll be even more practical when we can move to logical replication, so will be sticking with that for now.
> While Google has previously published papers describing some of its technologies, Google decided to take a different approach with Dataflow. Google open-sourced the SDK and model alongside commercialization of the idea and ahead of publishing papers on the topic.
A large number of ASF projects in the Big Data space are inspired by Google's publications. Good to see Google finally taking the lead and coming out with code.
The fact that both Atlassian and GitHub intended to unveil their own almost identical competing solutions, both built in Go, in consecutive sessions at the Git Merge conference (without either being aware of the other) is pretty hilarious.
That's been the norm for all new instances launched by AWS in the last couple years. They often follow that up after 6-12 months with ephemeral versions of these instance types.
Hopefully they continue to release instances with ephemeral storage, because most distributed systems design assumes uncorrated failure.
When I first encountered this behavior on BitBucket, I spent a lot of time reading the man pages and searching the internet trying to find out which option were they providing to `git diff` to get this diff output but couldn't find anything. Looks like there is indeed no such option. It would be awesome if git had something like `git diff branch-name --merge-commit-diff`.
It is misguiding to say that boto supports Python 3. The boto3 repository (https://github.com/boto/boto3) is experimental and far from feature completion. I am even not sure if it's API compatible with boto. Further, it has been dormant for quite some time.
What is it that makes a project go green on the wos?
These pull requests seem to indicate that someone has completed work on a whole bunch of other modules to make them Python 3 compatible but the pull requests have not yet been integrated.
Wow. I wonder what low-life downvoted this entirely innocent comment. Now continue with this one, surely you'll manage -60, especially if you have a voting ring.
Quick, it will likely be the only accomplishment you'll achieve today, if not for the rest of your life.
1) www.hnsearch.com had three sort options: relevance | date | points. It would be great if the new search also have all three options.
2) Please make your legacy style exactly like the old one. That style matched HN style perfectly. Right now there is an extra line which links to the HN thread (we are used to clicking the comments link for that) and the way comments are displayed feels not right.
We started using it recently and it's been amazing.