nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From olegz <>
Subject [GitHub] nifi pull request: NIFI-865 added initial support for AMQP publish...
Date Tue, 02 Feb 2016 17:11:35 GMT
Github user olegz commented on a diff in the pull request:
    --- Diff: nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/
    @@ -0,0 +1,219 @@
    + * 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
    + *
    + *
    + *
    + * 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.amqp.processors;
    +import java.lang.reflect.Method;
    +import java.util.ArrayList;
    +import java.util.Collections;
    +import java.util.HashSet;
    +import java.util.List;
    +import java.util.Map;
    +import java.util.Map.Entry;
    +import java.util.Properties;
    +import java.util.Set;
    +import org.apache.nifi.annotation.behavior.InputRequirement;
    +import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
    +import org.apache.nifi.annotation.documentation.CapabilityDescription;
    +import org.apache.nifi.annotation.documentation.Tags;
    +import org.apache.nifi.components.PropertyDescriptor;
    +import org.apache.nifi.components.Validator;
    +import org.apache.nifi.flowfile.FlowFile;
    +import org.apache.nifi.processor.ProcessContext;
    +import org.apache.nifi.processor.ProcessSession;
    +import org.apache.nifi.processor.Relationship;
    +import org.apache.nifi.processor.exception.ProcessException;
    +import org.apache.nifi.processor.util.StandardValidators;
    +import com.rabbitmq.client.AMQP;
    +import com.rabbitmq.client.AMQP.BasicProperties;
    + * Publishing AMQP processor which upon each invocation of
    + * {@link #onTrigger(ProcessContext, ProcessSession)} method will construct an
    + * AMQP message sending it to an exchange identified during construction of this
    + * class while transferring the incoming {@link FlowFile} to 'success'
    + * {@link Relationship}.
    + *
    + * Expects that queues, exchanges and bindings are pre-defined by an AMQP
    + * administrator
    + */
    +@Tags({ "amqp", "rabbit", "put", "message", "send", "publish" })
    +@CapabilityDescription("Creates a AMQP Message from the contents of a FlowFile and sends
the message to an AMQP Server")
    +public class PublishAMQP extends AbstractAMQPProcessor<AMQPPublisher> {
    +    public static final PropertyDescriptor EXCHANGE = new PropertyDescriptor.Builder()
    --- End diff --
    The motivation was that for 90% of the cases (in my experience) it will be required. No
one sends messages to a default exchange in prod, so this approach IMHO kind of speaks to
    Having said that I am ok with either, so let me know.

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 or file a JIRA ticket
with INFRA.

View raw message