AdamPurnomo commented on code in PR #14142: URL: https://github.com/apache/iceberg/pull/14142#discussion_r2471862661
########## api/src/main/java/org/apache/iceberg/catalog/CatalogObjectType.java: ########## @@ -0,0 +1,52 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ +package org.apache.iceberg.catalog; + +import java.util.Arrays; +import org.apache.iceberg.relocated.com.google.common.base.Preconditions; + +/** Enum representing {@link CatalogObject} type. */ +public enum CatalogObjectType { + NAMESPACE("namespace"), Review Comment: Q: Why do we have a name space type? In the spec `CatalogObjectUuid`, only to types are listed (`table` and `view`). Shouldn't namespace just extend `CatalogObject`? [Update]: After re-reading the spec, seems like it's true that the request can have 3 object types (`table`, `view` and `namespace`. However, `CatalogObjectUuid` only has 2 types (`table` and `view`). Reusing `CatalogObjectType` for the type in the `CatalogObjectUuid` means we could have an invalid type (`namespace`) for the uuid type. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
