Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[meta] 6.7.0 Release #3615

Closed
24 tasks done
codebrain opened this issue Mar 19, 2019 · 1 comment
Closed
24 tasks done

[meta] 6.7.0 Release #3615

codebrain opened this issue Mar 19, 2019 · 1 comment

Comments

@codebrain
Copy link
Contributor

codebrain commented Mar 19, 2019

Leftover Work

New Features 6.5.0

6.6.0

Breaking changes

Cross-cluster replication:

New features

Aggregations

Analysis:

Index Lifecycle Management:

Geo:

Search::

Enhancements

Aggregations

  • Handles exists query in composite aggs #35758 - No client implementation needed.

Authentication

Core

  • Added wait_for_metadata_version parameter to cluster state api. #35535

Cross-cluster replication

  • Add time since last auto follow fetch to auto follow stats #36542 (issues: #33007, #35895)

The last two removed CCR_AUTO_FOLLOW_POLL_INTERVAL which i think is returned on the ccr stats API's (investigate)

Bug fixes

Aggregations::

  • Fix MultiValuesSourceFieldConfig toXContent [#36525] (issue: [#36474]) - no change needed, server side issue

circuit breakers::

  • modify bigarrays to take name of circuit breaker [#36461] (issue: [#31435])

Core::

  • Suppress CachedTimeThread in hot threads output [#35558] (issue: [#23175])

Cross-cluster replication::

  • Add fatal_exception field for ccr stats in monitoring mapping [#37563]

Geo::

Rollup::

  • Fix Rollup's metadata parser [#36791] (issue: [#36726]) - no client changes needed

Search::

  • Inner hits fail to propagate doc-value format. (#36310) [#36355] (issue: [#36310]) - no client change needed, already in FieldJsonConverter
  • Fix custom AUTO issue with Fuzziness#toXContent [#35807] (issue: [#33462]) - no client change needed, server fix only

Do we expose doc value format on inner hit?

Snapshot/Restore::

  • Register Azure max_retries setting [#35286] - no client change needed
@codebrain codebrain changed the title [meta] 6.6.1 Release [meta] 6.7.0 Release Mar 19, 2019
@russcam russcam added the v6.7.0 label Mar 27, 2019
russcam added a commit that referenced this issue Mar 27, 2019
russcam added a commit that referenced this issue Mar 29, 2019
This commit adds custom rules to machine learning
detectors. The name of types used closely follows those
used in Elasticsearch source.

Relates: #3615
russcam added a commit that referenced this issue Apr 1, 2019
russcam added a commit that referenced this issue Apr 1, 2019
russcam added a commit that referenced this issue Apr 1, 2019
* Add ML filters APIs

This commit adds the Put, Get, Update and Delete filters APIs,
required for working with ML detector custom rules

* Add ML detector custom rules

This commit adds custom rules to machine learning
detectors. The name of types used closely follows those
used in Elasticsearch source.

* Remove "integer" from API generator

"integer" is no longer a type used within the spec

Relates: #3615
russcam added a commit that referenced this issue Apr 1, 2019
russcam added a commit that referenced this issue Apr 1, 2019
* Add ML filters APIs

This commit adds the Put, Get, Update and Delete filters APIs,
required for working with ML detector custom rules

* Add ML detector custom rules

This commit adds custom rules to machine learning
detectors. The name of types used closely follows those
used in Elasticsearch source.

* Remove "integer" from API generator

"integer" is no longer a type used within the spec

Relates: #3615
russcam added a commit that referenced this issue May 8, 2019
russcam added a commit that referenced this issue May 8, 2019
* Add ML filters APIs

This commit adds the Put, Get, Update and Delete filters APIs,
required for working with ML detector custom rules

* Add ML detector custom rules

This commit adds custom rules to machine learning
detectors. The name of types used closely follows those
used in Elasticsearch source.

* Remove "integer" from API generator

"integer" is no longer a type used within the spec

Relates: #3615
russcam added a commit that referenced this issue May 9, 2019
russcam added a commit that referenced this issue May 9, 2019
* Add ML filters APIs

This commit adds the Put, Get, Update and Delete filters APIs,
required for working with ML detector custom rules

* Add ML detector custom rules

This commit adds custom rules to machine learning
detectors. The name of types used closely follows those
used in Elasticsearch source.

* Remove "integer" from API generator

"integer" is no longer a type used within the spec

Relates: #3615
@codebrain codebrain mentioned this issue May 14, 2019
48 tasks
@codebrain
Copy link
Contributor Author

Superceded by: #3747

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants