You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by l vic <lv...@gmail.com> on 2019/01/10 19:18:03 UTC
merging with default values?
I have to merge results of 3 different queries into one flowfile....
The problem happens if some of the queries result in empty resultset. For
example, suppose i have 3 incoming connections for MergeContent:
query1->flowfile1/attribute1, query2->flowfile2/attribute2,
query3->flowfile3/attribute3
And query2 returns empty resultset. In this case attribute2 never shows up
in the merged flowfile.
Can someone recommend merge solution where i would always have attribute2
in the result but with some default value ( empty string assuming
attribute2 is text)?
Thank you...
Re: merging with default values?
Posted by l vic <lv...@gmail.com>.
Yes i do know them ahead of time, UpdateAttribute rules might work.
Thank you
On Thu, Jan 10, 2019 at 2:46 PM Russ Weiher <Ru...@progenity.com>
wrote:
> Do you know the name of the attributes you are looking for ahead of time?
> If so, the UpdateAttribute processor has an “Advanced” section that lets
> you write conditional rules based on flowfile attributes and properties.
> If you haven’t already checked that out, it might be a good place to
> start. There are some good examples in the NiFi documentation for that
> processor.
>
>
>
> *Russ Weiher*
>
> BI CI Solutions Architect
> Progenity, Inc.
>
>
>
> *From:* l vic [mailto:lvic4594@gmail.com]
> *Sent:* Thursday, January 10, 2019 2:18 PM
> *To:* users@nifi.apache.org
> *Subject:* merging with default values?
>
>
>
> I have to merge results of 3 different queries into one flowfile....
>
> The problem happens if some of the queries result in empty resultset. For
> example, suppose i have 3 incoming connections for MergeContent:
>
> query1->flowfile1/attribute1, query2->flowfile2/attribute2,
> query3->flowfile3/attribute3
>
> And query2 returns empty resultset. In this case attribute2 never shows up
> in the merged flowfile.
>
> Can someone recommend merge solution where i would always have attribute2
> in the result but with some default value ( empty string assuming
> attribute2 is text)?
>
> Thank you...
> IMPORTANT: This email (and any attachments) is intended for the use of
> only the person or entity to which it is addressed, and may contain
> information that is privileged and confidential. You, the recipient, are
> obligated to maintain it in a safe, secure and confidential manner.
> Unauthorized redisclosure or failure to maintain confidentiality may
> subject you to federal and state penalties. If you are not the intended
> recipient, please immediately notify us by return email, and delete this
> message from your computer.
>
RE: merging with default values?
Posted by Russ Weiher <Ru...@progenity.com>.
Do you know the name of the attributes you are looking for ahead of time? If so, the UpdateAttribute processor has an “Advanced” section that lets you write conditional rules based on flowfile attributes and properties. If you haven’t already checked that out, it might be a good place to start. There are some good examples in the NiFi documentation for that processor.
Russ Weiher
BI CI Solutions Architect
Progenity, Inc.
From: l vic [mailto:lvic4594@gmail.com]
Sent: Thursday, January 10, 2019 2:18 PM
To: users@nifi.apache.org
Subject: merging with default values?
I have to merge results of 3 different queries into one flowfile....
The problem happens if some of the queries result in empty resultset. For example, suppose i have 3 incoming connections for MergeContent:
query1->flowfile1/attribute1, query2->flowfile2/attribute2, query3->flowfile3/attribute3
And query2 returns empty resultset. In this case attribute2 never shows up in the merged flowfile.
Can someone recommend merge solution where i would always have attribute2 in the result but with some default value ( empty string assuming attribute2 is text)?
Thank you...
IMPORTANT: This email (and any attachments) is intended for the use of only the person or entity to which it is addressed, and may contain information that is privileged and confidential. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. Unauthorized redisclosure or failure to maintain confidentiality may subject you to federal and state penalties. If you are not the intended recipient, please immediately notify us by return email, and delete this message from your computer.