eric-maynard commented on code in PR #922: URL: https://github.com/apache/polaris/pull/922#discussion_r1979901757
########## service/common/src/main/java/org/apache/polaris/service/events/BeforeTableRefreshEvent.java: ########## @@ -0,0 +1,29 @@ +/* + * 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.polaris.service.events; + +import org.apache.iceberg.catalog.TableIdentifier; + +/** + * Emitted when Polaris intends to refresh its known version of a table's metadata by fetching the + * latest. + * + * @param tableIdentifier The identifier of the table being refreshed. + */ +public record BeforeTableRefreshEvent(TableIdentifier tableIdentifier) {} Review Comment: I wouldn't say each event is totally different -- they always have a time, they could have a stack trace, etc. But yes, primarily I think just having a marker interface would be helpful. For example, see [this method](https://spark.apache.org/docs/3.5.4/api/java/org/apache/spark/scheduler/SparkListener.html#onOtherEvent-org.apache.spark.scheduler.SparkListenerEvent-) in the Spark event listener interface that accepts a generic "Event" -- 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]
