The Distributed SQL Blog

Thoughts on distributed databases, open source and cloud native

YugaByte DB Engineering & Community Update – July 19, 2019

VP Marketing and Community

YugaByte DB Release Updates

We are pleased to announce that YugaByte DB 1.3.0 is live! You can read the release notes of this and previous versions here. This release is shipping with 24 new features, enhancements and bug fixes. Beyond enhancements and fixes, the other big news is that we have open sourced the entire core database code! This means that previously closed features like distributed backups, data encryption and replicas are now open sourced. This also means that upcoming features like change data capture and 2 datacenter deployments will open source as well. You can read more about why we decided to make this licensing change by checking out “Why we changed YugaByte DB licensing to 100% open source.”

This release also brings us closer to our 2.0 release at the end of the Summer in which the YSQL API will become generally available.

What’s YSQL? It’s YugaByte DB’s PostgreSQL-compatible, distributed SQL API.

To learn more about what’s shipping in the 2.0 release check out “YugaByte DB 2.0: A Distributed SQL Roadmap.

Now, let’s highlight a few items in this release:

[#1656] Enable DO statements (a.k.a Anonymous Blocks)

In PostgreSQL, DO statements execute “anonymous code blocks” in any of the supported PostgreSQL procedural languages. The code block itself treated as though it were the body of a function with no parameters, returning void. These anonymous code blocks are parsed and executed just once. One popular way to make use of a DO statement is to rather than create a function, call the function, and then drop (or just ignore) the function that you’ll never need again, it’s easier to simply call a single statement. Here’s a simple test of a DO statement:

Thanks to @bllewell for reporting the issue.

[#999] Allow SELECT from sequences
[#1003] Add support for setval()

In a nutshell, the CREATE SEQUENCE command creates a new sequence number generator. This involves creating and initializing a new special single-row table. After a sequence is created, you can use the functions nextval, currval, and setval to operate on the sequence. With the resolution of issue #999, you can now also SELECT from a sequence, for example:

With the resolution of issue #1003, setval()is now supported. For example:

Thanks to @hectorgcr for reporting these two issues.

New Documentation, Blogs, Tutorials, and Videos

New Blogs

New Docs

Upcoming Meetups and Conferences

We will be at a number of conferences and meetups over the next few months, below are some select few with the highlights. Do stop by, say hello and ask us any questions you have.

Distributed SQL Summit at PostgresConf Silicon Valley

PostgreSQL Meetups

SpringOne Tour

SpringOne Platform

AWS re:Invent

Dec 2-7: Las Vegas

We are Hiring!

YugaByte is growing fast and we’d like you to help us keep the momentum going! Check out our currently open positions:

Our team consists of domain experts from leading software companies such as Facebook, Oracle, Nutanix, Google and LinkedIn. We have come a long way in a short time but we cannot rest on our past accomplishments. We need your ideas and skills to make us better at every function that is necessary to create the next great software company. All while having tons of fun and blazing new trails!

Get Started

Ready to start exploring YugaByte DB features? Getting up and running locally with a three node cluster on your laptop is fast. Just download, extract, create the cluster, check its status and your ready to go!

What’s Next?

  • Using YugaByte at your company? Tell us about it and we’ll send you a hoodie!
  • Compare YugaByte DB in depth to databases like CockroachDB, Google Cloud Spanner and MongoDB.
  • Get started with YugaByte DB on macOS, Linux, Docker, and Kubernetes.
  • Contact us to learn more about licensing, pricing or to schedule a technical overview.

Related Posts

VP Marketing and Community