[fix][admin][branch-2.10] getMessageIdByTimestamp cannot redirect

[liudezhi2098]

Motivation

pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/v2/PersistentTopics.java

Lines 1758 to 1774 in fd7e0b4

	internalGetMessageIdByTimestamp(timestamp, authoritative)
	.thenAccept(messageId -> {
	if (messageId == null) {
	asyncResponse.resume(new RestException(Response.Status.NOT_FOUND, "Message ID not found"));
	} else {
	asyncResponse.resume(messageId);
	}
	})
	.exceptionally(ex -> {
	if (isNot307And404Exception(ex)) {
	log.error("[{}] Failed to get message ID by timestamp {} from {}",
	clientAppId(), timestamp, topicName, ex);
	resumeAsyncResponseExceptionally(asyncResponse, ex);
	}
	return null;
	});
	}

L1770 introduced by cherry-pick<#21995>, the forwarding will not be performed.

Modifications

adjust logic

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository:

[congbobo184]

this test don't verify this fix

[liudezhi2098]

Hi，where is it not covered?

[congbobo184]

you should check the 307And404Exception also can return the response exception right?

[liudezhi2098]

yes, the requested admin address is not the Broker to which the Topic belong, will the result be successful.
however, there is no 404 verification.

[congbobo184]

LGTM! nice cherry pick