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

    https://github.com/apache/nifi/pull/233#discussion_r54099029
  
    --- Diff: 
nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/put/sender/ChannelSender.java
 ---
    @@ -0,0 +1,103 @@
    +/*
    + * 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.processor.util.put.sender;
    +
    +import org.apache.nifi.logging.ProcessorLog;
    +
    +import java.io.IOException;
    +import java.nio.charset.Charset;
    +
    +/**
    + * Base class for sending messages over a channel.
    + */
    +public abstract class ChannelSender {
    --- End diff --
    
    Just a general comment. Unless you already know that this class should be 
public, consider reducing visibility. We can always make it public, but we can 
never go the other direction. Not sure if it applies here. . . your call.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to