32128894a5
This is an issue where a bucket can have both interim results and non-interim results, a bucket should never have both at the same time. The steps to cause this situation are: 1. Flush a running job and create interim results 2. Close that job (this does not delete interim results) 3. Re-open the job and POST data 4. The job will eventually emit a bucket result which mingles with the existing interim results Normally interim results are deleted by AutoDetectResultProcessor when a bucket is parsed following a flush command. Because of the close and re-opening of the job AutoDetectResultProcessor no longer knows that a previous flush command creating interim results. The fix is to always delete interim results the first time AutoDetectResultProcessor sees a bucket. relates elastic/x-pack-elasticsearch#1188 Original commit: elastic/x-pack-elasticsearch@5326455f54 |
||
|---|---|---|
| .. | ||
| bin/x-pack | ||
| bwc-zip | ||
| config/x-pack | ||
| keys | ||
| licenses | ||
| src | ||
| build.gradle | ||