Skip to content

/ cockroach

CockroachDB - the open source, cloud-native distributed SQL database.

www.cockroachlabs.com
View license
19.2k stars 2.4k forks
Star
Watch
master
77 branches 225 tags
Go to file
Code
Clone

Use Git or checkout with SVN using the web URL.

Latest commit

craig[bot] @itsbilal
@tbg @rytaft
4 authors Merge #55708 #55734 #55739
d58b0dc Oct 20, 2020
Merge #55708 #55734 #55739 
55708: storage: Use batches for direct RocksDB mutations r=itsbilal a=itsbilal

Currently, doing direct mutations on a RocksDB instance bypasses
custom batching / syncing logic that we've built on top of it.
This, or something internal to RocksDB, started leading to some bugs
when all direct mutations started passing in WriteOptions.sync = true
(see #55240 for when this change went in).

In this change, direct mutations still commit the batch with sync=true
to guarantee WAL syncing, but they go through the batch commit pipeline
too, just like the vast majority of operations already do.

Fixes #55362.

Release note: None.

55734: server: skip unit'ed engines in tombstone storage r=irfansharif a=tbg

Empty (i.e. uninitialized engines) could receive tombstones before
being initialized. Initialization checks that the engine is empty
(save for the cluster version) and thus failed. Simply don't write
tombstones to uninitialized engines, which is fine since by the
time the callbacks fire, at least one is initialized anyway, and
besides, this mechanism is best effort.

The alternatives would have been to either allow tombstones to
be present on an engine that is being bootstrapped, or to give
the storage the option to defer writing to the engine once it's
bootstrapped. Neither seemed worth the extra work.

Fixes #55576.

Release note: None


55739: opt: fix normalization of st_distance when use_spheroid parameter used r=rytaft a=rytaft

This commit fixes the normalization rule that converts `st_distance` to
`st_dwithin` or `st_dwithinexclusive`, which was broken in the case when
the `use_spheroid` parameter was used. Prior to this commit, the rule was
assigning the `use_spheroid` parameter as the 3rd parameter to `st_dwithin`
or `st_dwithinexclusive` and the `distance` parameter as the 4th, but that
order does not match the function signatures. This commit fixes the issue
by assigning `distance` as the 3rd parameter and `use_spheroid` as the 4th
if it exists.

Fixes #55675

Release note (bug fix): Fixed an internal error that could occur during
query planning when the use_spheroid parameter was used in the ST_Distance
function as part of a filter predicate. For example, `SELECT ... WHERE
ST_Distance(geog1, geog2, false) < 10` previously caused an error. This
has now been fixed.

Co-authored-by: Bilal Akhtar <bilal@cockroachlabs.com>
Co-authored-by: Tobias Grieger <tobias.b.grieger@gmail.com>
Co-authored-by: Rebecca Taft <becca@cockroachlabs.com>
d58b0dc

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
.github
CODEOWNERS: subscribe cli-prs to pkg/server/
Oct 19, 2020
build
Merge #55223
Oct 13, 2020
c-deps
storage: Use batches for direct RocksDB mutations
Oct 20, 2020
cloud
Merge #55451 #55464
Oct 12, 2020
docs
Merge #55567 #55604 #55616 #55737
Oct 20, 2020
githooks
docs: add API items to git commit scripts
Sep 23, 2020
licenses
licenses: Update BSL change date for master/21.1
Sep 8, 2020
monitoring
monitoring: add context for K8s alert
Sep 1, 2020
pkg
Merge #55708 #55734 #55739
Oct 20, 2020
scripts
Merge #54661
Sep 29, 2020
vendor @ 5d84f81
deps: bump cgosymbolizer
Oct 10, 2020
.editorconfig
opt: use 4 space indentation for .opt files
Apr 11, 2020
.gitattributes
colexec,coldata: check in generated code
Jun 25, 2020
.gitignore
*: include bazel in .gitignore
Oct 16, 2020
.gitmodules
Makefile: compile GEOS on Windows
Jun 26, 2020
.node-version
build: upgrade to node 12 LTS
Jan 22, 2020
AUTHORS
Merge #54667
Sep 22, 2020
CONTRIBUTING.md
Added link to the to-do apps repo
Sep 13, 2020
LICENSE
licenses: Add BSL.txt
Jun 4, 2019
Makefile
Makefile: add execgen to help output
Oct 9, 2020
README.md
docs: enhance the contributor guide
Jun 3, 2020
TEAMS.yaml
codeowners: enrich CODEOWNERS with team info and a debugging tool
Aug 19, 2020
go.mod
deps: bump cgosymbolizer
Oct 10, 2020
go.sum
deps: bump cgosymbolizer
Oct 10, 2020

README.md

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

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.

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 Deployments - 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?

Building from source

See our wiki for more details.

Contributing

We welcome your contributions! If you're looking for issues to work on, try looking at the good first issue list. We do our best to tag issues suitable for new external contributors with that label, so it's a great way to find something you can help with!

See our wiki for more details.

Engineering discussion takes place on our public mailing list, cockroach-db@googlegroups.com, and feel free to join our Community Slack (there's a dedicated #contributors channel!) to ask questions, discuss your ideas, or connect with other contributors.

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, check out CockroachDB in Comparison.

See Also

About

CockroachDB - the open source, cloud-native distributed SQL database.

www.cockroachlabs.com

Topics

go database sql distributed-database cockroachdb hacktoberfest

Resources

Readme

License

View license

Releases

225 tags

Packages

No packages published

Contributors 358

+ 347 contributors

Languages

You can’t perform that action at this time.