Skip to content

Releases: talariadb/talaria

v1.2.6

04 Apr 09:03
aaadbf3
Compare
Choose a tag to compare

This release contains the Parquet support for the ingestion (#62) , allowing Talaria to directly read and ingest Parquet files into its storage layer.

v1.2.5

17 Mar 07:03
804ed1d
Compare
Choose a tag to compare

This release contains the upgrade of ORC reader in order to fix the reader of float64 as well as a fix for some of our unit tests #61.

v1.2.4

08 Dec 03:29
f397161
Compare
Choose a tag to compare

This release contains various bug fixes.

  • Added support for map[string]interface{} to being auto-serialized into JSON for Golang client #54
  • Fix filter to return nil when data is filtered out #53 by
  • Fix sub streaming not starting #52

v1.2.3

19 Nov 07:18
5dc6756
Compare
Choose a tag to compare

This release adds real-time sub-streaming capability to Talaria. This can be configured per-table by using streams configuration.

Example configuration

tables:
  eventlog:
    streams:
      - pubsub:
          project: my-gcp-project
          topic: my-topic
          filter: "gcs://my-bucket/my-function.lua"
          encoder: json
...

Changelog

  • Streaming capability for Sinks.
  • Added Google Pub/Sub as a possible sub-streaming sink.

v1.2.2

18 Nov 06:51
6ccf06d
Compare
Choose a tag to compare

This release adds WithLoadBalancer option to the Golang client of talaria, allowing to specify clientside load balancing strategy.

v1.2.1

16 Nov 05:21
c196141
Compare
Choose a tag to compare

Changelog

This release fixes the following changes:

  • When querying, empty frames will be ignored which previously resulted in a panic.
  • When ingesting a varchar column, allow for schema re-mapping so that it can be converted to JSON, int32 or other types.
  • Golang client for Talaria now includes kubernetes resolver, allowing to Dial() with kubernetes schema. See: https://github.com/sercand/kuberesolver

v1.2.0

13 Nov 09:30
8818924
Compare
Choose a tag to compare

This version adds a support for multiple tables and ultimately introduces ability to re-partition data automatically by multiple different dimensions, during the ingestion process. For example, data can be partitioned by event, booking, and user_id by providing a following configuration:

tables:
  events:
    hashBy: "event"
    sortBy: "ingested_at"
  bookings: 
    hashBy: "booking_id"
    sortBy: "ingested_at"
  users: 
    hashBy: "user_id"
    sortBy: "ingested_at"

Breaking changes:

  • Environment variable configuration TALARIA_CONF prefix is replaced with TALARIA
  • Table configuration has been revamped (see /config/sample_config.yaml)
  • Removed the ability to configure logs and nodes tables as they were never actually changed
  • Compaction configuration is now per table

v1.1.18

15 Oct 03:07
1d356dc
Compare
Choose a tag to compare
  • Added Talaria Sink in order to re-publish compacted data into a second Talaria

v1.1.17

07 Aug 08:51
40a515c
Compare
Choose a tag to compare
  • Support JSON string input if desired static schema column is JSON #39

v1.1.16

30 Jul 09:11
d745aee
Compare
Choose a tag to compare
  • Increased compression chunk in ORC in order to support large strings.