[improve][admin] Enable users to specify TTL options in units other than seconds

[massakam]

Motivation

There were some options that weren't fixed in the previous PR, so I fixed them as well as the other options.

Verifying this change

• Make sure that the change passes the CI checks.

Documentation

• doc

[yuruguo]

LGTM, and I left a minor suggestion

[massakam]

PTAL

[315157973]

Will there be compatibility issues? Some scripts written by users cannot be used now because they do not contain units.

[massakam]

No, it's compatible. If the option does not contain a unit, its value is treated as a number of seconds.

pulsar/pulsar-common/src/main/java/org/apache/pulsar/common/util/RelativeTimeUtil.java

Lines 31 to 67 in 34673dd

	public static long parseRelativeTimeInSeconds(String relativeTime) {
	if (relativeTime.isEmpty()) {
	throw new IllegalArgumentException("expiry time cannot be empty");
	}
	int lastIndex = relativeTime.length() - 1;
	char lastChar = relativeTime.charAt(lastIndex);
	final char timeUnit;
	if (!Character.isAlphabetic(lastChar)) {
	// No unit specified, assume seconds
	timeUnit = 's';
	lastIndex = relativeTime.length();
	} else {
	timeUnit = Character.toLowerCase(lastChar);
	}
	long duration = Long.parseLong(relativeTime.substring(0, lastIndex));
	switch (timeUnit) {
	case 's':
	return duration;
	case 'm':
	return TimeUnit.MINUTES.toSeconds(duration);
	case 'h':
	return TimeUnit.HOURS.toSeconds(duration);
	case 'd':
	return TimeUnit.DAYS.toSeconds(duration);
	case 'w':
	return 7 * TimeUnit.DAYS.toSeconds(duration);
	// No unit for months
	case 'y':
	return 365 * TimeUnit.DAYS.toSeconds(duration);
	default:
	throw new IllegalArgumentException("Invalid time unit '" + lastChar + "'");
	}
	}