lkuchars commented on code in PR #10105: URL: https://github.com/apache/nifi/pull/10105#discussion_r2254263537
########## nifi-extension-bundles/nifi-standard-services/nifi-schema-registry-service-api/src/main/java/org/apache/nifi/schemaregistry/services/MessageNameResolver.java: ########## @@ -0,0 +1,50 @@ +/* + * 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.nifi.schemaregistry.services; + +import org.apache.nifi.controller.ControllerService; + +import java.io.IOException; +import java.io.InputStream; + +/** + * A service interface for resolving message names from schema definitions and input streams. + * This interface is typically used in scenarios where message types need to be determined + * dynamically from the content of the message and the associated schema definition. + * <p> + * Implementations of this interface can be used to extract or derive message names from + * various sources such as message headers, content, or schema metadata, enabling proper + * message processing and routing based on the resolved message type. + * </p> + */ +public interface MessageNameResolver extends ControllerService { + + /** + * Resolves and returns the message name based on the provided schema definition and input stream. + * <p> + * This method analyzes the given schema definition and input stream to determine the appropriate + * message name. The resolution strategy depends on the specific implementation and may involve + * parsing message headers, analyzing message content, or consulting schema metadata. Review Comment: Done -- 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]
