Pilosa 1.0 Released

Pilosa 1.0 Released

7/10/2018 • 2 min read

Pilosa is happy to announce version 1.0, available as of last week! After eight feature-heavy major releases since our launch, there were a lot of loose ends to clean up. As followers of semantic versioning, 1.0 is a big milestone, and a binding one. Although Pilosa is far from “complete”, this release signifies a certain stability. We plan to support the current feature set and API through all 1.x releases, and that entails more than you might think.

What’s in an API, anyway? The more we thought about that question, the more answers popped up. There is an obvious place to start—our HTTP interface and query language—but it keeps going. Since we’re an open-source project, the code itself is another facet of the API. Every public line of code is potentially a part of the API surface that requires support throughout 1.x.

Among the components we considered, as we were going into 1.0:

  • Query language
  • CLI usage
  • Configuration
  • Data storage format
  • Golang package structure and exported variables
  • Multiple language-specific clients, officially supported and otherwise
  • Pilosa dev kit, which includes examples and connectors

As we approached our 1.0 release, the ability to maintain compatibility promises became increasingly important. We began to audit all of these components for long-term support, with the primary goal of paring things down to our core functionality. Each of these components of our API surface has its own quirks, so they each need special attention.

A large portion of the work in this release focused on these API changes, but there were some more publicly visible changes as well:

  • PQL syntax has been updated significantly. See the docs for details.
  • Frames are now known as fields, and the nesting of fields within frames no longer exists; each field exists at the top level in an index.
  • Field creation has been revamped, with a more sensible field type system. For example, fields that were “rangeEnabled” are now simply fields of type “int”.
  • Slices are now known as shards.
  • Query responses now refer to “columns” rather than “bits”.
  • WebUI has been removed from Pilosa, and is now available separately.


To see the complete list of new features, fixes, and performance improvements, check out our releases on Github.

Get even more from Pilosa

Stay updated on our progress and upcoming events.