nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From olegz <>
Subject [GitHub] nifi pull request: NIFI-1028 initial commit of NiFi In Depth docum...
Date Mon, 18 Apr 2016 17:53:45 GMT
Github user olegz commented on a diff in the pull request:
    --- Diff: nifi-docs/src/main/asciidoc/nifi-in-depth.adoc ---
    @@ -0,0 +1,209 @@
    +// 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.
    +Apache NiFi In Depth
    +Apache NiFi Team <>
    +This advanced level document is aimed at providing an in-depth look at the implementation
and design decisions of NiFi. It assumes the reader has read enough of the other documentation
to know the basics of NiFi.
    +FlowFiles are at the heart of NiFi and its flow-based design. A FlowFile is just a collection
of attributes and a pointer to content, which is associated with one or more provenance events.
The attributes are key/value pairs that act as the metadata for the FlowFile, such as the
FlowFile filename. The content is the actual data or the payload of the file. Provenance is
a record of what’s happened to the FlowFile. Each one of these parts has its own repository
(repo) for storage.
    --- End diff --
    May be instead of "FlowFile is just a collection of attributes and a pointer to content"
use "FlowFile is a data record which consists of pointer to the content (payload) and attributes
to support such content". The ordering of _content_ then _attributes_ is also important, otherwise
what I am reading is that "FlowFile is just attributes. . ."

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