Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-8562

Apply version/tagging of data based upon a flow "revision" that generated it

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • MiNiFi
    • None

    Description

      Given the disparate and potentially disconnected nature of instances, it may configuration updates may not reach their intended targets leading to a potential range of versions. To this end, an operator that is collecting this information may wish to prioritize or even drop data that is beyond a certain range of versions.

      This requires a couple components:

      First, a mechanism of versioning/tagging flows is needed. This could be a hash or similar of the current contents, deferring ordering to another mechanism. Second, a way of tagging the generated information for that flow must occur on the agent. This additional information could potentially be amortized across an aggregation of data depending on the mechanism by which data is transmitted back to a central aggregation point.

      Attachments

        Activity

          People

            Unassigned Unassigned
            aldrin Aldrin Piri
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: