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

Allow PutKudu to take RecordPath for determining Operation Type and data to insert

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.13.0
    • Extensions
    • None

    Description

      PutKudu is Record oriented. But the Operation Type is specified as a property that can be configured using EL, which means that all operations for a given FlowFile must have the same Operation Type - it cannot vary per Record.

      It would be helpful to allow users to use RecordPath to configure the operation type and the data to insert. For example, we could have a record like:

      {
        "data": {
          "name": "John Doe",
           "id": 45
        },
        "metadata": {
          "operation": "insert"
        }
      }
      

      And then configure PutKudu to use a RecordPath of `/metadata/operation` for dictating the Operation Type and `/data` for dictating the data to insert.

      Attachments

        Issue Links

          Activity

            Commit 74968991d5034c96c481386f76929e9a49cab8a1 in nifi's branch refs/heads/main from Mark Payne
            [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7496899 ]

            NIFI-7952: Allow RecordPath to be used for specifying the Insertion Operation and the data to be inserted into Kudu

            jira-bot ASF subversion and git services added a comment - Commit 74968991d5034c96c481386f76929e9a49cab8a1 in nifi's branch refs/heads/main from Mark Payne [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7496899 ] NIFI-7952 : Allow RecordPath to be used for specifying the Insertion Operation and the data to be inserted into Kudu

            People

              markap14 Mark Payne
              markap14 Mark Payne
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 40m
                  40m