The Wayback Machine - https://web.archive.org/web/20190531113323/https://github.com/cockroachdb/cockroach
Skip to content

/cockroach

CockroachDB - the open source, cloud-native SQL database.
go database sql distributed-database cockroachdb
  1. Go 92.2%
  2. TypeScript 3.7%
  3. C++ 1.4%
  4. Yacc 0.9%
  5. Shell 0.3%
  6. Tcl 0.3%
  7. Other 1.2%
Branch: master
Find File
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Open in Desktop Download ZIP

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching Xcode...

If nothing happens, download Xcode and try again.

Launching Visual Studio...

If nothing happens, download the GitHub extension for Visual Studio and try again.

craig[bot] @mjibson
craig[bot] and mjibson Merge #37901 
37901: sql/distsqlrun: don't inspect encoding output during distinct r=mjibson a=mjibson

In the beginning of times a commit was added to teach DISTINCT about
the difference between filter columns and selected columns. In that
commit a check was added [1] such that the seen marker would only be
added if the encoded version of the column contained > 0 bytes. That
commit doesn't suggest a reason for the addition of that check, and it
is unclear to me now why it was added. (Note that I don't have experience
in the distsql directories, so I may be missing some history.) This file
has been improved since then, but the diligently check remained.

That check caused a GROUP BY with two rows each of empty arrays to not
consider those arrays equal (again, since the seen marker was avoided). A
experiment removing the check showed that no existing tests failed as
a result. And in addition, this new failing test now passed. I can't
find any evidence that this check was necessary, or why it was present
in the first place. I conclude that it is safe to remove until we find
a counter example.

Fixes #37544

[1]: 965107f#diff-6a63b13f6fae0ef7417b27292db3f04aR130

Release note (bug fix): Fix GROUP BY for empty arrays.

Co-authored-by: Matt Jibson <matt.jibson@gmail.com>
Latest commit a059c2e May 30, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github stats: add sql-opt-prs as code owner of /pkg/sql/stats Mar 14, 2019
build build: whitelist `prefix` Make variable May 1, 2019
c-deps libroach: enable rocksdb WAL recycling May 22, 2019
cloud cloud: bump Orchestrator configs to v19.1.0 Apr 30, 2019
docs Merge #37784 May 24, 2019
githooks githooks: make prepare-commit-msg resilient to `commit -v` Sep 10, 2018
licenses ui: regenerate fonts Nov 26, 2018
monitoring monitoring: add expiration alerts for optional certificates. Aug 13, 2018
pkg Merge #37901 May 30, 2019
scripts scripts: Recognize a few more licenses May 29, 2019
vendor @ 9e6cae8 lint: switch to new staticcheck May 12, 2019
.editorconfig editorconfig: Use tabs for Makefile indentation Mar 5, 2019
.gitattributes sql: clean up the `array` logic test Mar 13, 2019
.gitignore cmd/docgen: add grammar diagram generator Oct 4, 2017
.gitmodules ccl/gssapiccl: add GSS authentication support on Linux Feb 25, 2019
AUTHORS adding myself to authors May 28, 2019
CONTRIBUTING.md Merge #35028 Mar 1, 2019
Gopkg.lock lint: switch to new staticcheck May 12, 2019
Gopkg.toml lint: switch to new staticcheck May 12, 2019
LICENSE *: clarify licensing Nov 10, 2017
Makefile exec: implement MIN/MAX aggregations May 28, 2019
README.md README: remove links to gitter Mar 4, 2019

README.md

CockroachDB

CockroachDB is a cloud-native SQL database for building global, scalable cloud services that survive disasters.

TeamCity CI GoDoc

What is CockroachDB?

CockroachDB is a distributed SQL database built on a transactional and strongly-consistent key-value store. It scales horizontally; survives disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention; supports strongly-consistent ACID transactions; and provides a familiar SQL API for structuring, manipulating, and querying data.

For more details, see our FAQ or architecture document.

Here’s a quick explainer video:

Status

CockroachDB is production-ready. See our Roadmap for a list of features planned or in development.

Docs

For guidance on installation, development, deployment, and administration, see our User Documentation.

Quickstart

  1. Install CockroachDB.

  2. Start a local cluster and talk to it via the built-in SQL client.

  3. Learn more about CockroachDB SQL.

  4. Use a PostgreSQL-compatible driver or ORM to build an app with CockroachDB.

  5. Explore core features, such as data replication, automatic rebalancing, and fault tolerance and recovery.

Client Drivers

CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.

Deployment

  • Test Deployment - Easiest way to test an insecure, multi-node CockroachDB cluster.
  • Production Deployments
    • Manual - Steps to deploy a CockroachDB cluster manually on multiple machines.
    • Cloud - Guides for deploying CockroachDB on various cloud platforms.
    • Orchestration - Guides for running CockroachDB with popular open-source orchestration systems.

Need Help?

Contributing

We're an open source project and welcome contributions. See our Contributing Guide for more details.

Engineering discussion takes place on our public mailing list, cockroach-db@googlegroups.com.

Design

For an in-depth discussion of the CockroachDB architecture, see our Architecture Guide.

For the original design motivation, see our design doc.

Comparison with Other Databases

To see how key features of CockroachDB stack up against other databases, visit the CockroachDB in Comparison page on our website.

See Also

You can’t perform that action at this time.