Skip to content

First Major Release - BQL (expressions, free-form BQL queries), SizeIs, ContainsKey, ContainsValue. Ember 3 Octane!

Compare
Choose a tag to compare
@akshaisarma akshaisarma released this 13 Jan 01:19
· 12 commits to master since this release

This release updates to the major Bullet 1.0 rewrite and is compatible with APIs and Backends using Bullet components 1.0+. Notably, this release includes a way to write BQL (which is the only supported query format now in Bullet) queries through the UI. The QueryBuilder way of building queries is still fully supported (and augmented) but it cannot express everything BQL can.

  1. There is now a new BQL entry page for Queries that lets you write any BQL query that cannot be expressed in the Query Builder. The BQL entry page can autocomplete and understands your schema. The defaultQuery now allows you to only provide a static BQL query or an endpoint that provides a dynamic BQL query. The JSON format of queries is not supported.
  2. The QueryBuilder page now supports the rest of the filter operators (SizeIs, ContainsKey, ContainsValue) and is now fully type-aware allowing for the fully extended type-system that Bullet 1.0 provides. It only understands and works with the new way of specifying the columns from the API (or your own if you choose to roll your own). The QueryBuilder can also convert your queries to their BQL versions if you want to (the other way is not possible).
  3. Everything has been rewritten with native JS classes and uses Ember 3.20 with Glimmer components.
  4. Settings changes:
    • To Pass in the validation endpoint on the API, use validationPath. Defaults to validate-query
    • The units for everyForTimeBasedWindow has been changed to ms from secs. So multiply any existing values used by 1000
    • defaultQuery now only accepts a BQL string or a URL to fetch a BQL query.
    • The defaults for aggregationMaxSize has been changed from 512 to 500 and durationMaxSecs from 120 to 9007199254740 to match the defaults from bullet-core.

Due to the significant rewrite, both existing queries and results will be wiped when updating to this version from an existing version.