Docs: add known issue 65488 - SQL ignoring non-eq #65492
Conversation
Add description of the elastic#65488 known issue in release notes.
|
Pinging @elastic/es-docs (Team:Docs) |
Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
Add the known issue under following releasesȘ - 7.7.0 & .1 - 7.8.0 & .1 - 7.9.0 & .1 & .2 & .3 - 7.10.0
s/WHERE/`WHERE`
7.9.0 release had a "known issues" section already, place the SQL issue under that one instead of opening a new one.
|
@jrodewig, I was about to backport this change, but then not sure if necessary or beneficial[*] since that "code" - i.e. the release notes in pre 7.10 branches - won't get used again anymore. Still, let me know please if the practice is to do so in these circumstances. [*] ...as those branches will contain the note, but not the fix. |
|
@bpintea I think backporting only to 7.10 branches makes sense in that case. That approach also aligns with our docs backporting practices. |
* Docs: add known issue 65488 - SQL ignoring non-eq Add description of the elastic#65488 known issue in release notes. (cherry picked from commit 64ddf08)
* Docs: add known issue 65488 - SQL ignoring non-eq Add description of the #65488 known issue in release notes.
* Docs: add known issue 65488 - SQL ignoring non-eq Add description of the #65488 known issue in release notes.
* Docs: add known issue 65488 - SQL ignoring non-eq Add description of the #65488 known issue in release notes.
|
The docs team discussed our backport policy for known issues and decided to backport to any branch containing affected release notes. I backported this change to 7.9, 7.8, and 7.7. I also opened #73489 to clarify our backport policy. |
|
thanks, @jrodewig! |
Add description of the #65488 as a known issue in the release notes.