nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JPercivall <>
Subject [GitHub] nifi pull request #252: NIFI-615 - Create a processor to extract WAV file ch...
Date Wed, 15 Jun 2016 15:54:19 GMT
Github user JPercivall commented on a diff in the pull request:
    --- Diff: nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/
    @@ -0,0 +1,276 @@
    + * 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.
    + */
    +import java.util.ArrayList;
    +import java.util.Collections;
    +import java.util.HashMap;
    +import java.util.HashSet;
    +import java.util.List;
    +import java.util.Map;
    +import java.util.Set;
    +import java.util.concurrent.atomic.AtomicReference;
    +import java.util.regex.Pattern;
    +import org.apache.nifi.annotation.behavior.InputRequirement;
    +import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
    +import org.apache.nifi.annotation.behavior.SupportsBatching;
    +import org.apache.nifi.annotation.behavior.WritesAttribute;
    +import org.apache.nifi.annotation.behavior.WritesAttributes;
    +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.PropertyDescriptor;
    +import org.apache.nifi.flowfile.FlowFile;
    +import org.apache.nifi.flowfile.attributes.CoreAttributes;
    +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.ProcessorInitializationContext;
    +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.ObjectHolder;
    +import org.apache.tika.exception.TikaException;
    +import org.apache.tika.metadata.Metadata;
    +import org.apache.tika.parser.AutoDetectParser;
    +import org.apache.tika.sax.BodyContentHandler;
    +import org.xml.sax.SAXException;
    +@Tags({"media", "file", "format", "metadata", "audio", "video", "image", "document",
    +@CapabilityDescription("Extract the content metadata from flowfiles containing audio,
video, image, and other file "
    +        + "types.  This processor relies on the Apache Tika project for file format detection
and parsing.  It "
    +        + "extracts a long list of metadata types for media files including audio, video,
and print media "
    +        + "formats."
    +        + "For the more details and the list of supported file types, visit the library's
website "
    +        + "at")
    +@WritesAttributes({@WritesAttribute(attribute = "tika.<attribute>", description
= "The extracted content metadata "
    +        + "will be inserted with the attribute name \"tika.<attribute>\". ")})
    +public class ExtractMediaMetadata extends AbstractProcessor {
    +    public static final PropertyDescriptor MAX_NUMBER_OF_ATTRIBUTES = new PropertyDescriptor.Builder()
    +            .name("Max Number of Attributes")
    +            .description("Specify the max number of attributes to add to the flowfile.
There is no guarantee in what order"
    +                    + " the tags will be processed. By default it will process all of
    +            .required(false)
    +            .addValidator(StandardValidators.NON_NEGATIVE_INTEGER_VALIDATOR)
    +            .build();
    +    public static final PropertyDescriptor FILENAME_FILTER = new PropertyDescriptor.Builder()
    +            .name("File Name Filter")
    +            .description("A regular expression identifying file names which metadata
should extracted.  As flowfiles"
    +                    + " are processed, if the file name matches this regular expression
or this expression is"
    +                    + " blank, the flowfile will be scanned for it's MIME type and metadata.
 If left blank, all"
    +                    + " flowfiles will be scanned.")
    +            .required(false)
    +            .addValidator(StandardValidators.REGULAR_EXPRESSION_VALIDATOR)
    +            .build();
    +    public static final PropertyDescriptor MIME_TYPE_FILTER = new PropertyDescriptor.Builder()
    +            .name("MIME Type Filter")
    +            .description("A regular expression identifying MIME types for which metadata
should extracted.  Flowfiles"
    +                    + " selected for scanning by the File Name Filter are parsed to determine
the MIME type and extract"
    +                    + " metadata.  If the MIME type found matches this regular expression
or this expression is"
    +                    + " blank, the metadata keys that match the Metadata Key Filter will
be added to the flowfile"
    +                    + " attributes.  There is no guarantee in what order attributes will
be produced.  If"
    +                    + " left blank, metadata will be extracted from all flow files selected
for scanning.")
    +            .required(false)
    +            .addValidator(StandardValidators.REGULAR_EXPRESSION_VALIDATOR)
    +            .build();
    +    public static final PropertyDescriptor METADATA_KEY_FILTER = new PropertyDescriptor.Builder()
    +            .name("Metadata Key Filter")
    +            .description("A regular expression identifying which metadata keys received
from the parser should be"
    +                    + " added to the flowfile attributes.  If left blank, all metadata
keys parsed will be added to the"
    +                    + " flowfile attributes.")
    +            .required(false)
    +            .addValidator(StandardValidators.REGULAR_EXPRESSION_VALIDATOR)
    +            .build();
    --- End diff --
    Should support for expression language be added here? As an example, in the event multiple
different types of data are coming through one processor the user may want to construct the
regex using attributes on the flowfile

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