You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document dangers of backporting version-aware planning changes: a fix backported to a previous minor can be breaking if it's not in all subsequent patch versions of the next minor. Example: we implement a planner change in 9.3.1 and 9.2.2 - then a 9.2.2 coordinator will assume that the minimum version is 9.2.2, and thus all nodes can handle the new planning - but in fact, in the presence of 9.3.0 nodes, we may see serialization errors (or, worse, silently wrong results). ESQL: Add javadoc that explains version-aware planning #139706
Consequently, backporting version-dependent planning changes more than 1 minor is generally wrong.
Data types need to have an additional version that they're created on, so we can switch them off in SNAPSHOT-only bwc tests against older versions. ESQL: Add createdVersion for types #137432
Find out what to do with release bwc tests: e.g. release test for 9.3 against 9.2.1 will have the problem that 9.2.1 is actually on SNAPSHOT, and thus will consider under construction data types as supported. This already applies to AllSupportedFieldsTestCase and needs to be worked around right now; it will mess with our csv tests as well when we release the next data type (date_range).
We will either have to skip inconsistent configs (SNAPSHOT/SNAPSHOT is okay, release/release should be okay, mixed is not okay), or we have to adjust our release tests to build all clusters in release mode. Update: will skip only mixed snapshot/release clusters in ESQL: Enable AllSupportedFieldsTestCase in SNAPSHOT #139396; that should give us enough coverage; coverage is only missing for cases where we backport a change to an older branch AND this affects current main.
Consequently, backporting version-dependent planning changes more than 1 minor is generally wrong.
FROM remote:* | ...- without a single local index.FROMandENRICHFROMandENRICHFROMandLOOKUP JOINFROM remote:* | LOOKUP JOIN lu_idx ON ...Tests with subqueries; esp. ones where the subqueries use different index patterns in CCS, or some use ROW and others use FROM.-> [ES|QL] Support remote cluster in subqueries in from command #136035We will either have to skip inconsistent configs (SNAPSHOT/SNAPSHOT is okay, release/release should be okay, mixed is not okay), or we have to adjust our release tests to build all clusters in release mode.
Update: will skip only mixed snapshot/release clusters in ESQL: Enable AllSupportedFieldsTestCase in SNAPSHOT #139396; that should give us enough coverage; coverage is only missing for cases where we backport a change to an older branch AND this affects current main.