benesch

8 ms·

31.
by benesch 5y ago
Back when we announced Materialize we got the same question in reverse! You can read my response from a few years back here: https://news.ycombinator.com/item?id=22362301 Unfortunately I'm not privy to whatever improve
32.
by benesch 5y ago
- Materialize is not really focused on scaling because that is not really what it is for Horizontal scalability is actually something that Materialize's underlying incremental computation engine (timely/differential dataflow) exce
33.
by benesch 5y ago
> This change would break a lot of legacy code for no good reason Preventing a bug that occurs in 5% of observed codebases (and anecdotally, happens to me during development all the time) seems like about as good as reasons get. Swapping
34.
by benesch 5y ago
Funny, I bought a Brother HL-1240 for $15 off of Craigslist five years ago and it’s still going strong. Couldn’t be happier. So much so that I bought a USB-Ethernet adapter ( https://www.iogear.com/product/GPSU21/ )
35.
by benesch 5y ago
No, the OP is correct: the Go developers intentionally introduced randomness into map iteration order to shake out bugs. For evidence, see: https://github.com/golang/go/issues/6719 https://stackove
36.
by benesch 5y ago
Yes, exactly. Roughly speaking you'd see something like this: (id, text1, text2, timestamp, diff) ---- (42, before, data, Friday April 23 12:27AM, -1) (42, after, data, Friday April 23 12:27AM, +1)
37.
by benesch 6y ago
So, roughly speaking, I think you're describing a view that could be defined in Materialize like so: CREATE MATERIALIZED VIEW customer_avg_latency SELECT customer_id, metric_id, avg(metric_val) FROM metrics JOIN resou
38.
by benesch 6y ago
What you're asking about is the magic at the heart of Materialize. We're built atop an open-source incremental compute framework called Differential Dataflow [0] that one of our co-founders has been working on for ten years or so.
39.
by benesch 6y ago
Dremio is a batch processor, not a stream processor. The fundamental difference is that a batch processor will need to recompute a query from scratch whenever the input data changes, while a stream processor can incrementally update the exi
40.
by benesch 6y ago
(Disclaimer: I'm one of the engineers at Materialize.) > How does a company get funding for a feature that has already existed in other DBs for at least a decade? ... It's a cool concept but comes with huge caveats. I think you
41.
by benesch 6y ago
I’ve never understood the argument that floors and pavement are the cause of modern foot problems due to their hardness. It just doesn’t add up. Sure, running barefoot through a well-maintained soccer field is going to be lower impact than
42.
Debugging async generator errors in Rust(meltware.com)
3 points by benesch 6y ago|0 comments
43.
by benesch 6y ago
> I hit in Postgres recently that is terribly documented. I'm going to have to disagree with you there. This issue is quite well documented in the "SQL Functions Returning Sets" section [0]. The relevant bit starts thusly:
44.
by benesch 6y ago
Oh, wow, I didn't realize that incremental compiles for Chromium were what had inspired you to write Ninja! I'm a huge fan of Ninja. Composing a project of multiple shared libraries is a trick I've wanted to employ many times
45.
by benesch 6y ago
I wouldn't expect that to matter much during the debug cycle. The whole binary is going to be sitting in the buffer cache.
46.
by benesch 6y ago
Were you working on a C/C++ project, out of curiosity? Of the two projects I've meaningfully benchmarked gold on, one was written in Rust and one was written in Go. I can believe that the Rust/Go toolchains make life difficul
47.
by benesch 6y ago
That's not a stupid question. That's extremely insightful! That is exactly my model of the world, in fact. When linking incrementally, you don't want a tightly packed object file where the functions are stacked right on top o
48.
by benesch 6y ago
Yes, yes, yes, yes, yes. I'm going to make the kind of prediction that will set me up to be the laughingstock of HN in a few years. I think in-place binary patching will be the single most consequential development in build toolchains
49.
by benesch 6y ago
No, PostgreSQL definitely lets you do this. > An expression used inside a grouping_element can be an input column name, or the name or ordinal number of an output column (SELECT list item), or an arbitrary expression formed from input-co
50.
by benesch 6y ago
But the translation unit in Rust is the crate. Running `rustc` directly won't change that fact. Unlike in C, where you can compile TUs in any order since you've got interfaces in headers, in Rust you can't compile a crate u
51.
by benesch 6y ago
Part of what makes rustc's slow compile times so frustrating is that the slow compile times are mostly unrelated to all of the fancy compile-time analysis you listed. You can see this in action if you run `cargo check`. That will run a
52.
by benesch 6y ago
In PostgreSQL, the grammar does not permit unquoted identifiers to start with a digit. So this is a syntax error: SELECT 'val' AS 2 Instead you must escape the identifier with double quotes: SELECT 'val' A
53.
by benesch 6y ago
You can do that in PostgreSQL, but not according to the spec, apparently, and the PostgreSQL developers regret the feature. [0] (As someone who's spent a lot of time trying to simulate PostgreSQL's name resolution rules... it&#x27
54.
by benesch 6y ago
That is not correct. The parent has it right. The output is in fact sorted by the second field; it is not random. > Each expression can be the name or ordinal number of an output column (SELECT list item), or it can be an arbitrary exp
55.
by benesch 6y ago
You're not looking at the examples closely enough, if that's your takeaway. I assure you they are much weirder than forgetting to specify an ORDER BY clause and expecting sorted output.
56.
by benesch 6y ago
I highly recommend puzzling through some of these on your own first (it's a great way to build intuition for SQL's craziness), but here's a few explanations if you're stuck. jamie=# select a+1 from nums group by a+
57.
by benesch 6y ago
Yes, we consider ourselves an “open core” company. Timely and differential, the core compute engine, are fully open source projects, but the Materialize layer atop is licensed under the “Business Source License” (BSL). We think the BSL stri
58.
by benesch 7y ago
Good catch, thanks! I've filed an issue about this: https://github.com/MaterializeInc/materialize/issues/2056 Though it's not yet documented, we do support all of the SQL set operations [0]: UNION [
59.
by benesch 7y ago
> For example, if I rely on "updated-at" and infer that whatever record has the latest updated-at is the "current" record, then I may create the illusion that there are no gaps in my facts. That may not be so. I belie
60.
by benesch 7y ago
You would need to contact us to buy an enterprise license. (Or wait four years for the license to convert to Apache 2.)

More ›