Releases: terascope/teraslice
Releases · terascope/teraslice
v0.21.0
v0.20.0
- 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 - #572preserve_id
is no longer checked for - #444index
option no longer required on jobs that write to timeseries indices #431- A bug was fixed in the asset loader.
v0.19.0
v0.18.1
v0.18.0
-
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
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 ismonthly
. - Fixed bug with updating existing jobs #533
- Improved
/txt/slicers
by addingjob_id
andname
#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
v0.15.0
v0.14.0
First alpha release.
Initial alpha release with single node and clustering support.