[ANNOUNCE] Apache NiFi MiNiFi C++ 0.2.0 release

[Aldrin Piri]

Hello!

The Apache NiFi team would like to announce the release of Apache NiFi - MiNiFi 
C++ 0.2.0.

MiNiFi is a subproject of Apache NiFi.  MiNiFi provides a complementary data 
collection approach
that supplements the core tenets of NiFi in dataflow management, focusing on 
the collection
of data at the source of its creation.  The C++ implementation is to provide 
the same capabilities with a smaller footprint on systems where running a JVM 
is not practical or possible.

More details on Apache NiFi MiNiFi can be found here:
https://nifi.apache.org/minifi 

The release artifacts can be downloaded from here:
https://nifi.apache.org/minifi/download.html 


Issues closed/resolved for this list can be found here:
https://issues.apache.org/ 
jira/secure/ReleaseNote.jspa?version=12338790=12319921

Release note highlights can be found here:
https://cwiki.apache.org/ 
confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.2.0

Thank you!
The Apache NiFi team


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: configuring ConsumeImap with no password mailbox

[Matt Burgess]

Alternatively (in the Jira, e.g.) the field could be marked as
required(false), might be a better visual indicator to the user that
nothing need be entered in that field.

Regards,
Matt

On Fri, May 12, 2017 at 11:35 AM, Andy LoPresto  wrote:
> Aesha,
>
> The ConsumeIMAP processor extends AbstractEmailProcessor, which specifies
> password as a required and non-empty field. You would need to edit this file
> [1] and replace the validator StandardValidators.NON_EMPTY_VALIDATOR with
> Validator.VALID to always pass. If you rebuild and deploy the application,
> this should work.
>
> You can also file a Jira [2] to request this feature/improvement is added to
> the master branch.
>
> public static final PropertyDescriptor PASSWORD = new
> PropertyDescriptor.Builder()
> .name("password")
> .displayName("Password")
> .description("Password used for authentication and authorization
> with Email server.")
> .required(true)
> .expressionLanguageSupported(true)
> .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
> .sensitive(true)
> .build();
>
> [1]
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/AbstractEmailProcessor.java#L91-L91
> [2] https://issues.apache.org/jira/secure/CreateIssue!default.jspa
>
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On May 11, 2017, at 8:27 PM, Roy, Aesha Dhar  wrote:
>
> Hi,
>
> We have a process mailbox from which we want to consume all emails using
> nifi. The problem is that this mailbox does not have a password. But nifi
> does not allow me to configure the ConsumeImap without password.
> I tried putting some random password but I get connection exceptions with
> that.
>
> Is there some other way of connecting to this passwordless mailbox?
>
> Regards,
> Aesha
>
>
>

Controller service question

[Yuri Krysko]

Hello Devs,

I discovered Apache NiFi several days ago, parsed through all the docs and 
would like to ask for your opinion on my use-case. I plan to have several 
custom processors to do HTTP POSTs to a 3rd party ticketing system via its REST 
API based on the Flowfiles fed by other processors. In order to compose JSON 
payload messages and POST to this ticketing system, in addition to the 
FlowFiles, these custom processors require metadata info from the ticketing 
system. The metadata may or may not change over time, as it is potentially 
configurable by the ticketing system admins. I am wondering whether I should 
create a custom Controller service to pull the metadata and make it available 
to all interested processors? Can I include a Runnable task in the Controller 
service and have a configurable parameter of how often to pull the data?

Thank you,
Yuri



LEGAL DISCLAIMER: M.C. Dean, Inc. and its subsidiaries considers this e-mail 
and any files transmitted with it to be protected, proprietary or privileged 
information intended solely for the use of the named recipient(s). Any 
disclosure of this material or the information contained herein, in whole or in 
part, to anyone outside of the intended recipient or affiliates is strictly 
prohibited. M. C. Dean, Inc. accepts no liability for the content of this 
e-mail or for the consequences of any actions taken on the basis of the 
information contained in it, unless that information is subsequently confirmed 
in writing. Employees of M.C. Dean, Inc. are instructed not to infringe on any 
rights of the recipient; any such communication violates company policy. If you 
are not the intended recipient, any disclosure, copying, distribution, or 
action taken or omitted in reliance on this information is strictly prohibited 
by M.C. Dean, Inc.; please notify the sender immediately by return e-mail, 
delete this communication and destroy all copies.

Re: configuring ConsumeImap with no password mailbox

[Andy LoPresto]

Aesha,

The ConsumeIMAP processor extends AbstractEmailProcessor, which specifies 
password as a required and non-empty field. You would need to edit this file 
[1] and replace the validator StandardValidators.NON_EMPTY_VALIDATOR with 
Validator.VALID to always pass. If you rebuild and deploy the application, this 
should work.

You can also file a Jira [2] to request this feature/improvement is added to 
the master branch.

public static final PropertyDescriptor PASSWORD = new 
PropertyDescriptor.Builder()
.name("password")
.displayName("Password")
.description("Password used for authentication and authorization 
with Email server.")
.required(true)
.expressionLanguageSupported(true)
.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
.sensitive(true)
.build();

[1] 
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/AbstractEmailProcessor.java#L91-L91
 

[2] https://issues.apache.org/jira/secure/CreateIssue!default.jspa 



Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On May 11, 2017, at 8:27 PM, Roy, Aesha Dhar  wrote:
> 
> Hi,
> 
> We have a process mailbox from which we want to consume all emails using 
> nifi. The problem is that this mailbox does not have a password. But nifi 
> does not allow me to configure the ConsumeImap without password.
> I tried putting some random password but I get connection exceptions with 
> that.
> 
> Is there some other way of connecting to this passwordless mailbox?
> 
> Regards,
> Aesha
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: 1.2.0 upgrade label colors lost?

[Joe Gresock]

FYI, I updated firefox to 52.1.0 and the problem resolved.

On Thu, May 11, 2017 at 5:53 PM, Matt Gilman 
wrote:

> Thanks for the extra details. I think the issue is with your browser
> version. Other folks have reported similar issues [1]. While the browser
> version is unsupported [2], I've reopened the issue to investigate the
> underlying issue.
>
> Matt
>
> [1] https://issues.apache.org/jira/browse/NIFI-3829
> [2]
> https://nifi.apache.org/docs/nifi-docs/html/user-guide.
> html#browser-support
>
> On Thu, May 11, 2017 at 1:06 PM, Joe Gresock  wrote:
>
> > When I add a new label, it shows as clear on the main view, and default
> > yellow in the Navigate panel.
> >
> > When I load the page with the Web Console up, the colors are actually
> > there, and I don't get any console errors.  However, when I try to add a
> > new label, all the colors disappear from the main view (and still no
> > errors).
> >
> > Then, it gets stranger.  After I do this and then reload the screen, it
> > comes up with no colors with the Web Console up (still no errors).  When
> I
> > refresh again, the colors are back until I try to add a new label.
> >
> > I am using Firefox 45.8.0 on CentOS 6.8.
> >
> > On Thu, May 11, 2017 at 4:54 PM, Matt Gilman 
> > wrote:
> >
> > > Joe,
> > >
> > > When you add a new label, does it show as clear or the default yellow?
> > Are
> > > there any errors in the Console of your browser's Dev Tools? Does
> > Processor
> > > coloring work as expected? What browser are you using?
> > >
> > > Thanks
> > >
> > > Matt
> > >
> > > On Thu, May 11, 2017 at 12:37 PM, Joe Gresock 
> > wrote:
> > >
> > > > I just upgraded an existing NiFi 1.1.1 cluster to 1.2.0 and the label
> > > > colors appear to be gone.  I can see them in the Navigate view, but
> in
> > > the
> > > > main view the labels are just clear.  This also affects new labels
> > that I
> > > > add.
> > > >
> > > > I cleared my browser cache and reloaded with the same results.
> > > >
> > > > Has anyone else noticed this?
> > > >
> > > > Thanks,
> > > > Joe
> > > >
> > > > --
> > > > I know what it is to be in need, and I know what it is to have
> > plenty.  I
> > > > have learned the secret of being content in any and every situation,
> > > > whether well fed or hungry, whether living in plenty or in want.  I
> can
> > > do
> > > > all this through him who gives me strength.*-Philippians 4:12-13*
> > > >
> > >
> >
> >
> >
> > --
> > I know what it is to be in need, and I know what it is to have plenty.  I
> > have learned the secret of being content in any and every situation,
> > whether well fed or hungry, whether living in plenty or in want.  I can
> do
> > all this through him who gives me strength.*-Philippians 4:12-13*
> >
>



-- 
I know what it is to be in need, and I know what it is to have plenty.  I
have learned the secret of being content in any and every situation,
whether well fed or hungry, whether living in plenty or in want.  I can do
all this through him who gives me strength.*-Philippians 4:12-13*