nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From YolandaMDavis <>
Subject [GitHub] nifi pull request: NIFI-361 - Create Processors to mutate JSON dat...
Date Tue, 19 Apr 2016 19:46:40 GMT
Github user YolandaMDavis commented on a diff in the pull request:
    --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/
    @@ -0,0 +1,211 @@
    + * 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.processors.standard;
    +import java.util.ArrayList;
    +import java.util.Collections;
    +import java.util.HashSet;
    +import java.util.List;
    +import java.util.Set;
    +import java.util.concurrent.TimeUnit;
    +import org.apache.nifi.annotation.behavior.EventDriven;
    +import org.apache.nifi.annotation.behavior.InputRequirement;
    +import org.apache.nifi.annotation.behavior.SideEffectFree;
    +import org.apache.nifi.annotation.behavior.SupportsBatching;
    +import org.apache.nifi.annotation.documentation.CapabilityDescription;
    +import org.apache.nifi.annotation.documentation.Tags;
    +import org.apache.nifi.annotation.lifecycle.OnScheduled;
    +import org.apache.nifi.components.AllowableValue;
    +import org.apache.nifi.components.PropertyDescriptor;
    +import org.apache.nifi.components.ValidationContext;
    +import org.apache.nifi.components.ValidationResult;
    +import org.apache.nifi.components.Validator;
    +import org.apache.nifi.flowfile.FlowFile;
    +import org.apache.nifi.logging.ProcessorLog;
    +import org.apache.nifi.processor.AbstractProcessor;
    +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 org.apache.nifi.util.StopWatch;
    +import com.bazaarvoice.jolt.Shiftr;
    +import com.bazaarvoice.jolt.Removr;
    +import com.bazaarvoice.jolt.Chainr;
    +import com.bazaarvoice.jolt.Defaultr;
    +import com.bazaarvoice.jolt.Transform;
    +import com.bazaarvoice.jolt.JsonUtils;
    +@Tags({"json", "jolt", "transform", "shiftr", "chainr", "defaultr", "removr"})
    +@CapabilityDescription("Applies a list of JOLT specifications to the flowfile JSON payload.
A new FlowFile is created "
    +        + "with transformed content and is routed to the 'success' relationship. If the
JSON transform "
    +        + "fails, the original FlowFile is routed to the 'failure' relationship")
    +public class TransformJSON extends AbstractProcessor {
    +    public static final AllowableValue SHIFTR = new AllowableValue("Shift", "Shift Transform
DSL", "This JOLT transformation will shift input JSON/data to create the output JSON/data.");
    +    public static final AllowableValue CHAINR = new AllowableValue("Chain", "Chain Transform
DSL", "Execute list of JOLT transformations.");
    +    public static final AllowableValue DEFAULTR = new AllowableValue("Default", "Default
Transform DSL", " This JOLT transformation will apply default values to the output JSON/data.");
    +    public static final AllowableValue REMOVR = new AllowableValue("Remove", "Remove
Transform DSL", " This JOLT transformation will apply default values to the output JSON/data.");
    +    public static final PropertyDescriptor JOLT_SPEC = new PropertyDescriptor.Builder()
    +            .name("Jolt Specification")
    +            .description("Jolt Specification for transform of JSON data.")
    +            .required(true)
    +            .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
    +            .addValidator(new JOLTSpecValidator())
    +            .required(true)
    +            .build();
    --- End diff --
    Concerning pointing to a file I think that would be good on the single node model, however
could be more complicated in the cluster model (needing to ensure same file available to all
nodes processing the flow). Also I plan on working through a UI change, specific to this processor
at a later time, that I think will be helpful to users with complex specs.  One feature of
that UI could include the ability to locally point to the spec file and import into the UI,
which would then allow a user to edit if that like or simply save.  From there the imported
spec could be be saved as a property as it is currently.  

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