keith-turner commented on a change in pull request #1715: URL: https://github.com/apache/accumulo/pull/1715#discussion_r519059115
########## File path: core/src/main/java/org/apache/accumulo/core/spi/common/ContextClassLoaderFactory.java ########## @@ -0,0 +1,55 @@ +/* + * 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.accumulo.core.spi.common; + +import java.util.Map; +import java.util.function.Supplier; + +/** + * The ClassLoaderFactory is defined by the property general.context.factory. The factory + * implementation is configured externally to Accumulo and will return a ClassLoader for a given + * contextName. + * + * @since 2.1.0 + * + */ +public interface ContextClassLoaderFactory { + + /** + * Initialize the ClassLoaderFactory. Implementations may need a reference to the configuration so + * that it can clean up contexts that are no longer being used. + * + * @param contextProperties + * Accumulo configuration properties + * @throws Exception + * if error initializing ClassLoaderFactory + */ + void initialize(Supplier<Map<String,String>> contextProperties) throws Exception; Review comment: The concept that we know everything we may ever want to pass into a method is not something that has worked out too well in the past for the Accumulo API and its riddled with many duplicative overloaded methods as a result. The parameter interface is an attempt to avoid repeating a mistake that has been made many times in the past. I don't think there is a 0% chance that another parameter will ever be needed. While valid use case likely exists, we may or may not encounter them. I have no idea what the chances are, so I am ok w/ someone making the judgement call that its not worth worrying about. Personally I would worry about it simply based on past experience w/ API evolution. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
