@Override
    public FetchResponseData data() {
        return data;
    }
This wrapper supports all versions of the Fetch API

Possible error codes:

- {@link Errors#OFFSET_OUT_OF_RANGE} If the fetch offset is out of range for a requested partition
- {@link Errors#TOPIC_AUTHORIZATION_FAILED} If the user does not have READ access to a requested topic
- {@link Errors#REPLICA_NOT_AVAILABLE} If the request is received by a broker with version < 2.6 which is not a replica
- {@link Errors#NOT_LEADER_OR_FOLLOWER} If the broker is not a leader or follower and either the provided leader epoch
    matches the known leader epoch on the broker or is empty
- {@link Errors#FENCED_LEADER_EPOCH} If the epoch is lower than the broker's epoch
- {@link Errors#UNKNOWN_LEADER_EPOCH} If the epoch is larger than the broker's epoch
- {@link Errors#UNKNOWN_TOPIC_OR_PARTITION} If the broker does not have metadata for a topic or partition
- {@link Errors#KAFKA_STORAGE_ERROR} If the log directory for one of the requested partitions is offline
- {@link Errors#UNSUPPORTED_COMPRESSION_TYPE} If a fetched topic is using a compression type which is
    not supported by the fetch request version
- {@link Errors#CORRUPT_MESSAGE} If corrupt message encountered, e.g. when the broker scans the log to find
    the fetch offset after the index lookup
- {@link Errors#UNKNOWN_TOPIC_ID} If the request contains a topic ID unknown to the broker
- {@link Errors#FETCH_SESSION_TOPIC_ID_ERROR} If the request version supports topic IDs but the session does not or vice versa,
    or a topic ID in the request is inconsistent with a topic ID in the session
- {@link Errors#INCONSISTENT_TOPIC_ID} If a topic ID in the session does not match the topic ID in the log
- {@link Errors#UNKNOWN_SERVER_ERROR} For any unexpected errors
clients/src/main/java/org/apache/kafka/common/requests/FetchResponse.java