Skip to content

Releases: terascope/teraslice

v0.21.0

10 Oct 17:59
Compare
Choose a tag to compare
v0.21.0 Pre-release
Pre-release
  • Reverted code for elasticsearch_api revert resolves #579 (#580)
  • Stagger worker recycle (#575)

v0.20.0

29 Sep 21:10
Compare
Choose a tag to compare
v0.20.0 Pre-release
Pre-release
  • Updates jobs will now get validated - #568
  • Users will receive a sensible error message when trying to start non-existant jobs - #562
  • job_id is included in more log output - #572
  • preserve_id is no longer checked for - #444
  • index option no longer required on jobs that write to timeseries indices #431
  • A bug was fixed in the asset loader.

v0.19.0

29 Sep 21:12
Compare
Choose a tag to compare
v0.19.0 Pre-release
Pre-release

Included the following bug fixes

  • Elasticsearch reader fix (#564)
  • fixed schema validation and faulty regex (#561)

v0.18.1

20 Sep 00:13
Compare
Choose a tag to compare
v0.18.1 Pre-release
Pre-release
  • Fixed bad mapping on *__ex index
  • Changed the way the op_runner and job_runner use the terafoundation API #542

v0.18.0

18 Sep 22:23
Compare
Choose a tag to compare
v0.18.0 Pre-release
Pre-release
  • added minimum key depth paramter resolves #551

    Jared Noble - Mon, 18 Sep 2017 14:48:01 -0700

  • fixed returns on retries to not immediatly complete resolves #549

    Jared Noble - Fri, 15 Sep 2017 14:13:03 -0700

v0.17.0

16 Sep 00:33
Compare
Choose a tag to compare
v0.17.0 Pre-release
Pre-release

This release contains the following changes:

  • The Execution Contexts (ex in the code) have been moved from the *__jobs index to their own index *__ex #545
  • The job_id has been added to the analytics index. #544
  • The *__state and *__analytics indices are now time stamped and rolled over according to their specified or default frequency. The default for both is monthly.
  • Fixed bug with updating existing jobs #533
  • Improved /txt/slicers by adding job_id and name #536
  • The slicer no longer interacts with the cluster_master after the initial job is started #518
  • Slicers and workers can now be started stand alone, requiring only an environment variable set and the execution context present in the *__jobs index. #519

v0.16.0

09 Sep 01:02
Compare
Choose a tag to compare
v0.16.0 Pre-release
Pre-release

Adds worker_disconnect_timeout to the slicer which allows the recycle worker functionality to work in conjuntion with the behavior of the slicer terminating a job after all workers have died.

v0.15.0

07 Sep 22:56
Compare
Choose a tag to compare
v0.15.0 Pre-release
Pre-release
  • Slicer queue refactor
  • fixed race condition on job initialization resolves #524
  • if all workers disconnect, slicer will terminate resolves #253

v0.14.0

06 Sep 00:15
Compare
Choose a tag to compare
v0.14.0 Pre-release
Pre-release

This release fixes the following issues:

  • #454 - Multiple slicers running on the same job
  • #434 - Jobs won't stop when told to

First alpha release.

03 Aug 18:37
Compare
Choose a tag to compare
First alpha release. Pre-release
Pre-release

Initial alpha release with single node and clustering support.