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.

Sign up for GitHub

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

[DOCS] [7.x] Document deprecation of storing nanosecond resolution on date field #79554

Merged
merged 2 commits into from
Oct 20, 2021
Merged

[DOCS] [7.x] Document deprecation of storing nanosecond resolution on date field #79554

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9bf53fd
[DOCS] Document deprecation of storing nanosecond resolution on date …
pgomulka Oct 20, 2021
f9b3c05
Apply suggestions from code review
pgomulka Oct 20, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 17 additions & 3 deletions docs/reference/migration/migrate_7_16.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ logging>>.
====
*Details* +
In SAML, Identity Providers (IdPs) can either be explicitly configured to
release a `NameID` with a specific format, or configured to attempt to conform
release a `NameID` with a specific format, or configured to attempt to conform
with the requirements of a Service Provider (SP). The SP declares its
requirements in the `NameIDPolicy` element of a SAML Authentication Request.
In {es}, the `nameid_format` SAML realm setting controls the `NameIDPolicy`
Expand All @@ -103,9 +103,9 @@ IdP. If you want to retain the previous behavior, set `nameid_format` to

*Impact* +
If you currently don't configure `nameid_format` explicitly, it's possible
that your IdP will reject authentication requests from {es} because the requests
that your IdP will reject authentication requests from {es} because the requests
do not specify a `NameID` format (and your IdP is configured to expect one).
This mismatch can result in a broken SAML configuration. If you're unsure whether
This mismatch can result in a broken SAML configuration. If you're unsure whether
your IdP is explicitly configured to use a certain `NameID` format and you want to retain current behavior
, try setting `nameid_format` to `urn:oasis:names:tc:SAML:2.0:nameid-format:transient` explicitly.
====
Expand Down Expand Up @@ -347,4 +347,18 @@ cache do not expire.
To override the defaults, configure the `script.cache.max_size`,
`script.max_compilations_rate`, and `script.cache.expire` settings.
====

.Attempting to store nanosecond resolution in a date field is deprecated.
pgomulka marked this conversation as resolved.
Show resolved Hide resolved
[%collapsible]
====
*Details* +
Attempting to store a nanosecond resolution in a date field is deprecated.
pgomulka marked this conversation as resolved.
Show resolved Hide resolved
This behaviour was allowed so far, but was always resulting in resolution loss.
pgomulka marked this conversation as resolved.
Show resolved Hide resolved
A {ref}/date.html[`date`] field can only store up to millisecond resolutions.
*Impact* +
pgomulka marked this conversation as resolved.
Show resolved Hide resolved
If you attempt to store a nanosecond resolution in a `date` type field, {es} will
emit a deprecation warning. To avoid deprecation warnings, use a
{ref}/date_nanos.html[`date_nanos`] field instead.
====

// end::notable-breaking-changes[]