Re: nifi proxy issue + jira account

[Matt Burgess]

Kyle,

Per the new Apache Jira instructions [1], please provide the following
information to priv...@nifi.apache.org  and I can
create an account for you and add you as a
contributor:

- email address
- preferred username (N.B. hyphens not allowed)
- alternate username (in case the preferred one is already in use)
- display name, if it is different from the username


Regards,
Matt

[1] https://infra.apache.org/jira-guidelines.html#who

On Thu, Dec 15, 2022 at 4:43 PM Nguyen, Kyle 
wrote:

> Hi.  Thanks for maintaining the project.
>
>
>
> 1.   Can I get a jira account please?  Would like to request *
> StandardProxyConfigurationService* integration into 
> *StandardOath2AccessTokenProvider
> *and into *QuerySalesforceObject*
>
> 2.   Or perhaps you can help me more directly on this stackoverflow:
> https://stackoverflow.com/questions/74482819/connecting-to-an-external-http-api-behind-a-proxy-from-nifi
>
>
>
> I also tried this ENV VAR in my docker nifi instance.  It doesn’t work.
>
>
>
> JAVA_FLAGS=-Dhttp.nonProxyHosts="localhost,.amazonaws.com"
> -Dhttp.proxyHost=proxy.foo.com -Dhttp.proxyPort=3128 -Dhttp.proxyUser=foo
> -Dhttp.proxyPassword=bar
>
>
>
>
>
> [image: cid:17261f6184a4cff311]
>
> *Kyle Nguyen*
> Corporate Technology, Software Engineer
>
>
>
> *Millennium Management LLC*
>
> 399 Park Avenue  |  New York, NY 10022
>
> 📞 +1.212.708.1366  | 📱 +1.929.837.1788
>
> mlp.com 
>
>
>
>
>
> ##
>
> The information contained in this communication is confidential and
>
> may contain information that is privileged or exempt from disclosure
>
> under applicable law. If you are not a named addressee, please notify
>
> the sender immediately and delete this email from your system.
>
> If you have received this communication, and are not a named
>
> recipient, you are hereby notified that any dissemination,
>
> distribution or copying of this communication is strictly prohibited.
> ##
>
>

nifi proxy issue + jira account

[Nguyen, Kyle]

Hi.  Thanks for maintaining the project.


1.   Can I get a jira account please?  Would like to request 
StandardProxyConfigurationService integration into 
StandardOath2AccessTokenProvider and into QuerySalesforceObject

2.   Or perhaps you can help me more directly on this stackoverflow: 
https://stackoverflow.com/questions/74482819/connecting-to-an-external-http-api-behind-a-proxy-from-nifi

I also tried this ENV VAR in my docker nifi instance.  It doesn’t work.

JAVA_FLAGS=-Dhttp.nonProxyHosts="localhost,.amazonaws.com" 
-Dhttp.proxyHost=proxy.foo.com -Dhttp.proxyPort=3128 -Dhttp.proxyUser=foo 
-Dhttp.proxyPassword=bar


[cid:17261f6184a4cff311]

Kyle Nguyen
Corporate Technology, Software Engineer

Millennium Management LLC
399 Park Avenue  |  New York, NY 10022
📞 +1.212.708.1366  | 📱 +1.929.837.1788
mlp.com





##

The information contained in this communication is confidential and

may contain information that is privileged or exempt from disclosure

under applicable law. If you are not a named addressee, please notify

the sender immediately and delete this email from your system.

If you have received this communication, and are not a named

recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited.

##

[RESULT][VOTE] Adopt NiFi 2.0 Proposed Release Goals

[David Handermann]

Apache NiFi Community,

I am pleased to announce that the vote to adopt NiFi 2.0 Proposed Release
Goals passes:

[13] +1 binding votes
[11] +1 non-binding votes
[0] 0 votes
[0] -1 binding votes
[1] -1 non-binding vote

This vote signifies approval of the following actions:

1. Rename NiFi 2.0 Proposed Release Goals to NiFi 2.0 Release Goals
2. Create version 1 branch in Git for subsequent support releases on the
version 1 series
3. Update the current main branch in Git to version 2.0.0-SNAPSHOT

Thanks to everyone for the great participation and discussion!

I have renamed the Release Goals  pageto reflect approval [1] and I will
coordinate with Joe Witt on implementing actions 2 and 3.

The vote thread is available in the list archives:

https://lists.apache.org/thread/ycz0vm3jz4pjxntk03qxpw3gfbn3lmz3

[1] https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Release+Goals

Re: [VOTE] Adopt NiFi 2.0 Proposed Release Goals

[David Handermann]

+1 binding

Edward,

If you could provide some additional details in a new thread, that would be
helpful.  As stated, the primary purpose of the proposed goals is to reduce
technical debt without introducing too many breaking changes. Depending on
the components in question, there may be opportunity for some refactoring.

Regards,
David Handermann

On Wed, Dec 14, 2022 at 3:27 PM Zoltán Kornél Török 
wrote:

> +1 (non-binding)
>
> Nathan Gough  ezt írta (időpont: 2022. dec. 14., Sze,
> 20:46):
>
> > +1 (binding)
> >
> > The proposal sounds great to me
> >
> >
> >
> > On Wed, Dec 14, 2022, 1:01 PM Edward Armes 
> wrote:
> >
> > > -1 (non-binding)
> > >
> > > Im not sure if this is covered by 8 and 5 , but I would like to suggest
> > > that as part of 2.0 focus on removing places were concrete
> > implementations
> > > are used over interfaces, and update the way the website docs are
> > generated
> > > to ensure that NARs that not included in the standard distribution are
> > > included.
> > >
> > > I think this would allow for work of a NAR registry to happen outside
> of
> > a
> > > major release and allow for the potential consideration of individually
> > > versions components reducing the sizes of future releases.
> > >
> > > Edward
> > >
> > >
> > > On Mon, 12 Dec 2022, 20:32 Andrew Lim, 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > > On Dec 12, 2022, at 12:02 PM, David Handermann <
> > > > exceptionfact...@apache.org> wrote:
> > > > >
> > > > > Team,
> > > > >
> > > > > Following positive feedback on NiFi 2.0 Proposed Release Goals [1]
> on
> > > the
> > > > > recent discussion thread [2], I am calling this vote to adopt the
> > > > following
> > > > > as Release Goals for NiFi 2.0:
> > > > >
> > > > > 1. Remove Java 8 support and require Java 11
> > > > > 2. Remove deprecated components
> > > > > 3. Remove deprecated component properties
> > > > > 4. Remove components integrating with unmaintained services
> > > > > 5. Remove compatibility classes and methods
> > > > > 6. Remove flow.xml.gz in favor of flow.json.gz
> > > > > 7. Remove duplicative features
> > > > > 8. Upgrade internal Java API references
> > > > > 9. Reorganize standard components
> > > > > 10. Implement migration tools for upgrading flows
> > > > >
> > > > > A positive vote indicates agreement on these goals and the
> initiation
> > > of
> > > > > the following actions:
> > > > >
> > > > > 1. Rename NiFi 2.0 Proposed Release Goals to NiFi 2.0 Release Goals
> > > > > 2. Create version 1 branch in Git for subsequent support releases
> on
> > > the
> > > > > version 1 series
> > > > > 3. Update the current main branch in Git to version 2.0.0-SNAPSHOT
> > > > >
> > > > > The vote will be open for 72 hours and follow standard procedures
> for
> > > > > release votes.
> > > > >
> > > > > Please review the linked goals and discussions for background.
> > > > >
> > > > > [ ] +1 Adopt NiFi 2.0 Release Goals
> > > > > [ ] +0 No opinion
> > > > > [ ] -1 Do not adopt NiFi 2.0 Release Goals for the following
> > reasons...
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Proposed+Release+Goals
> > > > > [2]
> https://lists.apache.org/thread/xo77p9t3xg4k70356xrqbdg4m9sg7sf8
> > > >
> > > >
> > >
> >
>
>
> --
> Üdvözlettel,
> Török Zoltán Kornél
> 06-30-509-0541
>

Looking for clarity on using NiFi

[E M]

https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.EnforceOrder/

Fairly new with NiFi, looking for information that is just lacking.
I'm trying to do what I consider to be a very basic feat.
Get a bunch of files.
Sort those files by their name or whatever I want.
I found the documentation but it is just lacking.
For examples,
The documentation states to on the 'Initial Order'
When the first FlowFile of a group arrives, initial target order will be
computed and stored in the managed state. After that, target order will
start being tracked by EnforceOrder and stored in the state management
store. If Expression Language is used but evaluated result was not an
integer, then the FlowFile will be routed to failure, and initial order
will be left unknown until consecutive FlowFiles provide a valid initial
order.
*Supports Expression Language: true (will be evaluated using flow file
attributes and variable registry)*
and
The documentation states to on the 'Order Attribute'
A name of FlowFile attribute whose value will be used to enforce order of
FlowFiles within a group. If a FlowFile does not have this attribute, or
its value is not an integer, the FlowFile will be routed to failure.

Neither of these clearly present me with how to use this software.
It probably means more to someone who already knew how to do it and it just
is a reminder to them but for new people we are left scratching our heads.

I've been Googling for 3 hours trying to find an answer.
Can you clarify?


-- 
Respectfully,
Elijah