|
1 | 1 | // Use these for links to issue and pulls. Note issues and pulls redirect one to |
2 | 2 | // each other on Github, so don't worry too much on using the right prefix. |
3 | | -// :issue: https://github.com/elastic/elasticsearch/issues/ |
4 | | -// :pull: https://github.com/elastic/elasticsearch/pull/ |
| 3 | +//:issue: https://github.com/elastic/elasticsearch/issues/ |
| 4 | +//:ml-issue: https://github.com/elastic/ml-cpp/issues/ |
| 5 | +//:pull: https://github.com/elastic/elasticsearch/pull/ |
| 6 | +//:ml-pull: https://github.com/elastic/ml-cpp/pull/ |
5 | 7 |
|
6 | 8 | = Elasticsearch Release Notes |
7 | 9 |
|
8 | | -== Elasticsearch 7.0.0 |
| 10 | +//// |
| 11 | +// To add a release, copy and paste the following text, uncomment the relevant |
| 12 | +// sections, and add a link to the new section in the list of releases at the |
| 13 | +// top of the page. Note that release subheads must be floated and sections |
| 14 | +// cannot be empty. |
| 15 | +// TEMPLATE: |
9 | 16 |
|
10 | | -=== Breaking Changes |
| 17 | +// == {es} version n.n.n |
11 | 18 |
|
12 | | -=== Deprecations |
| 19 | +//=== Breaking Changes |
13 | 20 |
|
14 | | -=== New Features |
| 21 | +//=== Deprecations |
15 | 22 |
|
16 | | -=== Enhancements |
| 23 | +//=== New Features |
17 | 24 |
|
18 | | -=== Bug Fixes |
| 25 | +//=== Enhancements |
19 | 26 |
|
20 | | -=== Regressions |
| 27 | +//=== Bug Fixes |
21 | 28 |
|
22 | | -=== Known Issues |
| 29 | +//=== Regressions |
23 | 30 |
|
24 | | -== Elasticsearch version 6.4.0 |
25 | | - |
26 | | -=== New Features |
27 | | - |
28 | | -Detectors now support rules that allow the user to improve the results by providing some domain specific |
29 | | -knowledge in the form of rule. ({pull}119[#119]) |
30 | | - |
31 | | -=== Enhancements |
32 | | - |
33 | | -Improve and use periodic boundary condition for seasonal component modeling ({pull}84[#84]) |
34 | | -Improve robustness w.r.t. outliers of detection and initialisation of seasonal components ({pull}90[#90]) |
35 | | -Improve behavior when there are abrupt changes in the seasonal components present in a time series ({pull}91[#91]) |
36 | | -Explicit change point detection and modelling ({pull}92[#92]) |
37 | | -Improve partition analysis memory usage ({pull}97[#97]) |
38 | | -Reduce model memory by storing state for periodicity testing in a compressed format ({pull}100[#100]) |
39 | | -Improve the accuracy of model memory control ({pull}122[#122]) |
40 | | -Improve adaption of the modelling of cyclic components to very localised features ({pull}134[#134]) |
41 | | -Reduce the memory consumed by distribution models ({pull}146[#146]) |
42 | | - |
43 | | -Forecasting of Machine Learning job time series is now supported for large jobs by temporarily storing |
44 | | -model state on disk ({pull}89[#89]) |
45 | | - |
46 | | -Secure the ML processes by preventing system calls such as fork and exec. The Linux implemenation uses |
47 | | -Seccomp BPF to intercept system calls and is available in kernels since 3.5. On Windows Job Objects prevent |
48 | | -new processes being created and macOS uses the sandbox functionality ({pull}98[#98]) |
49 | | - |
50 | | -Fix a bug causing us to under estimate the memory used by shared pointers and reduce the memory consumed |
51 | | -by unnecessary reference counting ({pull}108[#108]) |
52 | | - |
53 | | -Reduce model memory by storing state for testing for predictive calendar features in a compressed format |
54 | | -({pull}127[#127]) |
55 | | - |
56 | | -=== Bug Fixes |
57 | | - |
58 | | -Age seasonal components in proportion to the fraction of values with which they're updated ({pull}88[#88]) |
59 | | -Persist and restore was missing some of the trend model state ({pull}#99[#99]) |
60 | | -Stop zero variance data generating a log error in the forecast confidence interval calculation ({pull}#107[#107]) |
61 | | -Fix corner case failing to calculate lgamma values and the correspoinding log errors ({pull}#126[#126]) |
62 | | -Influence count per bucket for metric population analyses was wrong and lead to wrong influencer scoring ({pull}#150[#150]) |
63 | | -Fix a possible SIGSEGV for jobs with multivariate by fields enabled which would lead to the job failing ({pull}#170[#170]) |
64 | | - |
65 | | -Correct the model bounds and typical value calculation for time series models which use a multimodal distribution. |
66 | | -This issue could cause "Unable to bracket left percentile =..." errors to appear in the logs. ({pull}#176[#176]) |
67 | | - |
68 | | -=== Regressions |
69 | | - |
70 | | -=== Known Issues |
71 | | - |
72 | | -== Elasticsearch version 6.3.0 |
73 | | - |
74 | | -=== New Features |
75 | | - |
76 | | -=== Enhancements |
77 | | - |
78 | | -=== Bug Fixes |
79 | | - |
80 | | -Function description for population lat_long results should be lat_long instead of mean ({pull}81[#81]) |
81 | | -By-fields should respect model_plot_config.terms ({pull}86[#86]) |
82 | | -The trend decomposition state wasn't being correctly upgraded potentially causing the autodetect process to abort ({pull}136[#136]) |
83 | | -Fix a SIGSEGV in the autodetect process when jump upgrading from 5.6 to 6.3 ({pull}143[#143]) |
84 | | - |
85 | | -=== Regressions |
86 | | - |
87 | | -=== Known Issues |
| 31 | +//=== Known Issues |
| 32 | +//// |
0 commit comments