News for hackers. Stuff that matters.
Re:The SQL layer in CockroachDB by irfansharif on Saturday April 22, 2017 @02:31AM (#14171362)
while there is an explicit delineation between the internal `kv` package[1] and the overarching `sql` one[2], your specific concern regarding a query optimizer is not strictly an isolated component at this moment in time. query optimizations, last I checked, was not an explicit pre-processing stage but rather done so when constructing the AST representation of the query with each node being an `iterator` as described in the Volcano Evaluation System paper[3]. there was some work underway to move towards an intermediate representation[4] to go through the standard query optimizations, no context into how far along this effort is.

[1]: https://github.com/cockroachdb/cockroach/tree/master/pkg/kv

[2]: https://github.com/cockroachdb/cockroach/tree/master/pkg/sql

[3]: https://paperhub.s3.amazonaws.com/dace52a42c07f7f8348b08dc2b...

[4]: https://github.com/cockroachdb/cockroach/pull/10055

Re:The SQL layer in CockroachDB by knz42 on Saturday April 22, 2017 @07:00AM (#14171965)
I wrote the rfc for this "effort": there will be an IR in CockroachDB, just not right now. It's a lot of work and we're not going to do this in one go.