[Improvement] Remove unnecessary metalake access in `CatalogManager`

### What would you like to be improved?

The following code will access and check Metalake twice, as the method `catalogInUse` will check metalake again.

https://github.com/apache/gravitino/blob/bd41384a6c1b92a96a6aefb6c54c0ffb748a2bff/core/src/main/java/org/apache/gravitino/catalog/CatalogManager.java#L562-L567


https://github.com/apache/gravitino/blob/bd41384a6c1b92a96a6aefb6c54c0ffb748a2bff/core/src/main/java/org/apache/gravitino/catalog/CatalogManager.java#L867-L870

### How should we improve?

_No response_

	checkMetalake(metalakeIdent, store);

	try {
	if (catalogInUse(store, ident)) {
	return null;
	}

	private boolean catalogInUse(EntityStore store, NameIdentifier ident)
	throws NoSuchMetalakeException, NoSuchCatalogException {
	NameIdentifier metalakeIdent = NameIdentifier.of(ident.namespace().levels());
	return metalakeInUse(store, metalakeIdent) && getCatalogInUseValue(store, ident);

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[Improvement] Remove unnecessary metalake access in `CatalogManager` #9562

What would you like to be improved?

How should we improve?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Improvement] Remove unnecessary metalake access in CatalogManager #9562

Description

What would you like to be improved?

How should we improve?

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

[Improvement] Remove unnecessary metalake access in `CatalogManager` #9562