Skip to content

Releases: parseablehq/parseable

Bug fix release v0.4.3

03 May 07:02
8cd8cce
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.4.2...v0.4.3

Bug fix release v0.4.2

27 Apr 11:10
b16e42f
Compare
Choose a tag to compare

The release v0.4.1 had an issue where data in staging directory was not cleaned up after it was pushed to backend storage. We recommend updating to this release to avoid this issue.

What's Changed

Full Changelog: v0.4.1...v0.4.2

v0.4.1

26 Apr 16:09
0ba1af0
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.4.0...v0.4.1

v0.4.0

03 Apr 12:33
f053d2f
Compare
Choose a tag to compare

Note

In previous releases, a json array like

{
	"name": "John",
	"age": 30,
	"cars": [{
			"brand": "Ford"
		},
		{
			"brand": "BMW",
			"model": "x1"
		},
		{
			"brand": "Audi",
			"model": "q1"
		}
	]
}

would be flattened to cars.0_brand,cars.0_model,
cars.1_brand, cars.1_model, cars.2_brand,
cars.2_model. This was an issue for very long
arrays, a single event with a long array could add
several columns to the schema. But most of the times these
columns would be empty.

This release changes the approach to flatten to two fields
like cars_brand, cars_model. Each column will have
an array of elements in that field.

Refer #344

What's Changed

New Contributors

Full Changelog: v0.3.0...v0.4.0

Bug fix release v0.3.0

13 Mar 03:22
30b4353
Compare
Choose a tag to compare

Important

This release fixes an issue with memory consumption while moving ingested data to Parquet and pushing the data
to storage backend.

What's Changed

Full Changelog: v0.2.2...v0.3.0

Feature release v0.2.2

19 Feb 07:59
a482faa
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.2.1...v0.2.2

Bugfix Release v0.2.1

10 Feb 16:26
8a10090
Compare
Choose a tag to compare

Highlight

Fix the issue with S3 mode where events were not uploaded to S3.

What's Changed

Full Changelog: v0.2.0...v0.2.1

v0.2.0

09 Feb 15:49
9110055
Compare
Choose a tag to compare

Highlights

Parseable server is now completely schema free. You can ingest logs with different schema to the same stream and seamlessly query all the logs. Before upgrading to this release, we recommend the below steps:

  1. Pause sending events to the Parseable server.
  2. Keeping running the server for few minutes (after pausing events). This will ensure there is no data present in the staging directory.
  3. Stop the server, replace the binary or update the image tag (in helm / k8s) and start the server.

What's Changed

New Contributors

Full Changelog: v0.1.1...v0.2.0

v0.1.1

16 Jan 01:39
8405d01
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.1.0...v0.1.1

v0.1.0

10 Jan 09:42
c285b1c
Compare
Choose a tag to compare

Backwards incompatibility

With this release, there are minor changes in how Parseable reads config files. Also, server now strictly checks the local stage and remote storage paths. These changes are backward incompatible - which means upgrading from older versions (v0.0.8 or older) will not work right out of the box.

But be assured that it is safe to upgrade. If you want to move from an older version and keep old data intact. Please join us on Slack, or create an issue on GitHub, and we'll help you right away.

What's Changed

Full Changelog: v0.0.8...v0.1.0