Class EsqlResolveFieldsResponse
java.lang.Object
org.elasticsearch.transport.TransportMessage
org.elasticsearch.transport.TransportResponse
org.elasticsearch.action.ActionResponse
org.elasticsearch.xpack.esql.action.EsqlResolveFieldsResponse
- All Implemented Interfaces:
Writeable,org.elasticsearch.core.RefCounted
-
Nested Class Summary
Nested classes/interfaces inherited from class org.elasticsearch.action.ActionResponse
ActionResponse.EmptyNested classes/interfaces inherited from interface org.elasticsearch.common.io.stream.Writeable
Writeable.Reader<V>, Writeable.Writer<V> -
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final TransportVersionMarks when we started using the minimum transport version to determine whether a data type is supported on all nodes.Fields inherited from interface org.elasticsearch.core.RefCounted
ALWAYS_REFERENCED -
Constructor Summary
ConstructorsConstructorDescriptionEsqlResolveFieldsResponse(FieldCapabilitiesResponse caps, TransportVersion minTransportVersion) -
Method Summary
Modifier and TypeMethodDescriptioncaps()The minimumTransportVersionof all clusters against which we resolved indices.voidwriteTo(StreamOutput out) Methods inherited from class org.elasticsearch.transport.TransportMessage
decRef, hasReferences, incRef, tryIncRefMethods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.elasticsearch.core.RefCounted
mustIncRef
-
Field Details
-
RESOLVE_FIELDS_RESPONSE_USED_TV
Marks when we started using the minimum transport version to determine whether a data type is supported on all nodes. This is about the coordinator - data nodes will be able to respond with the correct data as long as they're on the transport version required for the respective data types. SeeDataType.supportedVersion().Note: this is in 9.2.1, but not 9.2.0 - in 9.2.0 we resorted to workarounds to sometimes enable
DataType.DENSE_VECTORandDataType.AGGREGATE_METRIC_DOUBLE, even though 9.2.0 nodes already support these types.This means that mixed clusters with a 9.2.1 coordinator and 9.2.0 data nodes will properly support these types, but a 9.2.0 coordinator with 9.2.1+ nodes will still require the workaround.
-
-
Constructor Details
-
EsqlResolveFieldsResponse
public EsqlResolveFieldsResponse(FieldCapabilitiesResponse caps, TransportVersion minTransportVersion) -
EsqlResolveFieldsResponse
- Throws:
IOException
-
-
Method Details
-
writeTo
- Throws:
IOException
-
caps
-
minTransportVersion
The minimumTransportVersionof all clusters against which we resolved indices.If this is
nullthen one of the nodes is beforeRESOLVE_FIELDS_RESPONSE_CREATED_TVbut we have no idea how early it is. Could be back in8.19.0.
-