v0.12.5

Continuing the sandbox improvements to streamline the creation process for our users 😎

Full Changelog: v0.12.4...v0.12.5

v0.12.4

Get started in our sandbox environment. Upgrade when you’re ready. We grow when you grow.

What's Changed

• New rotational.io pricing page links added to footer by @daniellemaxwell in #824
• Tenant cleanup script by @pdeziel in #825 🧹

Full Changelog: v0.12.3...v0.12.4

v0.12.3

Want to feel like a kid again? Stop by the Ensign Sandbox and start experimenting ☀️ No need to worry, and at no cost to you.

The Ensign U curriculum is available and filled with tips and guidance. Need a little more help to start building? Reach out to us at support@rotational.io or schedule a quick chat. We've got your back 😉

Full Changelog: v0.12.2...v0.12.3

v0.12.2

v0.12.2 includes improvements to the Topic Creation and API Key Creation workflows, increased frequency of updates to data in the events table, as well as a streamlined workflow for users to accept invites and collaborate with additional teams and organizations within Ensign!

Full Changelog: v0.12.1...v0.12.2

v0.12.1

Just a few improvements to the Ensign UI to ensure the best experience for our users 💙

Full Changelog: v0.12.0...v0.12.1

v0.12.0

Automated deduplication on topics is now available 🏋️ Let Ensign do the heavy lifting by managing data quality issues without you having to write custom code.

No need to worry about duplicate data in data sources that you are ingesting data from. We have several options that not only give you a lot of flexibility, but give you the ability to switch from one option to another without concern over data loss.

We've also made a lot of improvements to Ensign core including adding a memory efficient task scheduler, and the ability to destroy event objects when a topic is deleted. We've improved a lot of the internal functionality to make things faster, more efficient, and more consistent, and have fixed several bugs.

Automated Deduplication Options

There are a lot of ways to determine if two events are duplicates of each other. Ensign uses user-defined policies to figure out duplication. Policies you can set are:

• Strict: Two events with identical metadata, data, mimetype, and type (though provenance, region, publisher, encryption, etc. may differ).
• Datagram: Two events with identical data regardless of metadata, mimetype, or type information
• Key Grouped: Two events with identical data and the same value for a user specified key or keys in the metadata
• Unique Key Constraint: Two events with the same value for specified key or keys in the metadata (unique key index)
• Unique Field Constraint*: Two events with the same value for a field or fields in the data (unique field index)
• None: We store all events no matter what

*Note that the unique field constraint requires us to be able to process your data -- which we won't be able to do until we have a schema registry. So although this is technically a deduplication option, in practice it is not usable and will return not implemented errors.

One quick caveat: deduplication happens as a background process right now, not in realtime. However in our next release, we will add real-time deduplication and data quality checks!

Ensign UX/UI Updates

• Beacon Home UI Improvements to allow users to easily view and change their settings
• Additional user support including helpful starter videos and increased accessibility to resources

Full Changelog: v0.11.0...v0.12.0

v0.11.0

Forgot your password? 🔐 We've got you covered. This release includes the password reset functionality, continued improvements to make rotational.io even more informative and user friendly, fixes to the login workflow, a fix for a pagination bug, increased code coverage on the frontend, and a new step-by-step guide in the docs!

Full Changelog: v0.10.0...v0.11.0

v0.10.0

Thanks for the feedback! We've been listening 😅 This release includes a streamlined registration workflow for new users where we've simplified account creation and provided helpful context, updates to PyEnsign for ease of use, website updates, and a search feature within the Ensign Documentation. Fixes have been added for a registration bug (thanks for the heads up Tamana!) and a BE core bug.

Ensign UX/UI Updates

• New Onboarding Workflow
• Improved Authentication Workflow
• Refactored Profile Page
• Improved Responsiveness of Blog Post Tags
• Blog Post Tags are now Clickable!
• Use Cases added to Rotational.io

Ensign Core Improvements

• Workspace Lookup Added to Quarterdeck
• Resend Verification Email Endpoint Added to Quarterdeck
• Update Organization Endpoint Added to Quarterdeck

Bug Fixes

• Name Group Error Fixed
• Fixed Invalid Timestamps in Acks

Full Changelog: v0.9.0...v0.10.0

v0.9.0

Oh dang, this is getting good...

Now you can peek into your Ensign Topics, poke around, and preview all kinds of data!

Ensign is now more like a database than ever before! Take advantage of EnSQL - a query language that you're already familiar with to fetch historic data from your topics and perform analytics to determine how your data is changing even faster! Want to know how many events or how much data storage your topic is taking? Our new topic detail page will not only give you all the details of the event types that you have published, but give you the ability to query them directly!

Looking for inspo? Check out The Data Playground, a curated set of data sources, asynchronous data science use cases, and sample code to help get you started. In just a few steps, generate a time-series dataset for analytics and modeling using Ensign!

Ensign UX/UI Updates

• Users can now easily navigate to the Topic Detail page
• Users can interact with their data inside of a topic to better understand what's happening inside of the topic and to see the default topic policies and settings
• Documentation refresh including additions to the Ensign FAQ page
• Schema diagrams have been added for each Data Playground data source, along with enhanced descriptions and use cases for each source
• Improvements to the registration process for new users - less clicks are required to create an account!
• Project detail page refactored with updated copy & removal of excess tooltips

Ensign Core Improvements

• Mimetype detection
• EnSQL
• New Broker system
• Enhanced topic and event storage
• Topic statistics such as number of events, duplicates, and amount of bytes stored are recorded
• Expanded test coverage

Bug Fixes

• Fixes to protocol buffer typos
• Better subscriber handling and error messages

Full Changelog: v0.8.1...v0.9.0

v0.8.0

Shhhh 🤫 we’ve been hard at work improving Ensign’s front and back ends. Nothing dramatic to announce just yet, but stay tuned 😉 

Ensign UI/UX Updates

• Better user experience for alerting in the Ensign user landing page and Project Details page.
• Modals are more uniform in size and appearance
• Preliminary Topic Detail page to aggregate key details about topics associated with a project
• Added the ability to revoke an API key
• Added endpoint to backend to fetch stats for topics
• Server-side token caching: better caching of user access tokens on the backend

Ensign Core Improvements

• Event persistence - events are written to disk
• New broker model - Ensign Core can handle consumer groups and disk writes
• New configuration management system and devOps usage tool (confire)
• Improved backup resiliency for both Ensign and Quarterdeck
• Implemented meta-event store in Ensign. Meta-events are events about Ensign

Bug Fixes

• Fixed rate limiting for interactions between Tenant and Quarterdeck

Full Changelog: v0.7.1...v0.8.0