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
We should increase test coverage a little bit more in AllSupportedFieldsTestCase. Recall, these tests guard against regressions of existing, simple queries when we roll out new data types, and thus prevent accidental breakage.
More test cases:
Enable ENRICH tests in AllSupportedFieldsTestCase on SNAPSHOT: requires updating the test cases for the new DATE_RANGE type. See disabled test cases here and here.
Bwc tests with union types, when one (or more) of the constituent types are only supported on the newer nodes
tests with subfields: a.b may have a supported type but a not and vice versa
Tests with CPS/remote indices aliased by a flat index name
CCQ tests where one cluster can already index EXPONENTIAL_HISTOGRAM (and any other new types that we'll add in the future) but another cluster is too old - the corresponding fields should be treated as UNSUPPORTED irrespective of whether the new or the old cluster is coordinating the query.
Follow-up to #137534.
We should increase test coverage a little bit more in AllSupportedFieldsTestCase. Recall, these tests guard against regressions of existing, simple queries when we roll out new data types, and thus prevent accidental breakage.
ENRICHtests in AllSupportedFieldsTestCase on SNAPSHOT: requires updating the test cases for the newDATE_RANGEtype. See disabled test cases here and here.a.bmay have a supported type butanot and vice versaEXPONENTIAL_HISTOGRAM(and any other new types that we'll add in the future) but another cluster is too old - the corresponding fields should be treated asUNSUPPORTEDirrespective of whether the new or the old cluster is coordinating the query._tsid