Skip to content

Releases: parseablehq/parseable

Feature Release v0.7.0

19 Sep 13:30
be6231c
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.6.2...v0.7.0

Bug fix release v0.6.2

19 Aug 11:56
9c31cd6
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.6.0...v0.6.2

Feature release v0.6.0

27 Jul 15:09
a35e07d
Compare
Choose a tag to compare

New Console

This release includes the fully redesigned console for Parseable. We're excited for you to try it out!

screenzy-1690470040075

What's Changed

Full Changelog: v0.5.1...v0.6.0

Bugfix Release v0.5.1

19 Jul 03:01
75e1ede
Compare
Choose a tag to compare

What's Changed

New Contributors

  • @czyt made their first contribution in #453

Full Changelog: v0.5.0...v0.5.1

Feature Release v0.5.0

11 Jun 07:19
3a2f9b7
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.4.4...v0.5.0

Bugfix release 0.4.4

18 May 06:02
bc81fc7
Compare
Choose a tag to compare

What's Changed

  • Retention config shouldn't need logstream to be initialized by @nitisht in #398
  • Add log stream creation and set retention in Helm Chart by @nitisht in #397
  • Update vergen to 8.1 and clean up version print mechanism by @nitisht in #400
  • Add ServiceMonitor object to allow service detection with Prometheus Operator by @nitisht in #401
  • Add load-test case for PRs by @Sajiyah-Salat in #404
  • Fix order for tests by @nitisht in #405
  • Fix broken link by @Sajiyah-Salat in #407
  • Replace mutable buffer with concat_batches by @trueleo in #402
  • Remove in memory ingestion and query by @trueleo in #413
  • Remove the env var and cli option for memory only ingestion by @nitisht in #414

New Contributors

Full Changelog: v0.4.3...v0.4.4

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