Github user jtstorck commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/2475#discussion_r168895945
  
    --- Diff: 
nifi-api/src/main/java/org/apache/nifi/annotation/behavior/HighResourceUsageScenario.java
 ---
    @@ -0,0 +1,51 @@
    +/*
    + * 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.annotation.behavior;
    +
    +import java.lang.annotation.Documented;
    +import java.lang.annotation.ElementType;
    +import java.lang.annotation.Inherited;
    +import java.lang.annotation.Repeatable;
    +import java.lang.annotation.Retention;
    +import java.lang.annotation.RetentionPolicy;
    +import java.lang.annotation.Target;
    +
    +/**
    + * Annotation that may be placed on a
    + * {@link org.apache.nifi.components.ConfigurableComponent Component} 
indicating that this
    + * component may cause high usage of a resource.
    + */
    +@Documented
    +@Target({ElementType.TYPE})
    +@Retention(RetentionPolicy.RUNTIME)
    +@Inherited
    +@Repeatable(HighResourceUsageScenarios.class)
    +public @interface HighResourceUsageScenario {
    --- End diff --
    
    I'm not tied to any of the names of classes that I've used so far.  
SystemResourceConsideration sounds good to me, especially since it has a wider 
range of meaning than just specifying higher resource usage.


---

Reply via email to