There had been a lot of internal discussions at work about the actual life
cycle of the class instance instantiated by NiFi; and the variables scoped at
the class level. When do Processors "reset", are new instances created for each
run, or are instances recycled? What about concurrent threads
Hello Chris,
Did you find a solution for this? I looked at the underlying Apache
HttpComponents API, and found InputStreamBody class.
InputStreamBody doesn't copy whole byte array, but it streams data
from specified input stream to the output stream per 4kb.
You may find this example useful, the
Still good. Was looking through tickets yesterday and today and while
review progress has been made on some PRs, it might be best to move JIRAs
tagged for 1.4.0 that have PRs and aren't on the cusp of being committed to
post 1.4.0. Thoughts?
On Mon, Sep 18, 2017 at 2:50 PM Joe Witt
Definitely agree with Brandon that due for a 1.4.0 and it has some
really nice things in it
Jeff Storck volunteered to RM. Jeff you still good? Anything I can help with?
Thanks
Joe
On Mon, Sep 18, 2017 at 2:28 PM, Brandon DeVries wrote:
> There are significant changes in
There are significant changes in 1.4.0 that I am actively waiting on...
On Mon, Sep 18, 2017 at 2:25 PM Russell Bateman
wrote:
> I don't know. Are we due for a release? Is time-since the significant
> factor in a release cycle or is growing features part of it?
>
> 1.3.0
I don't know. Are we due for a release? Is time-since the significant
factor in a release cycle or is growing features part of it?
1.3.0 subsists with no bump of the third digit. This is an oddly stable
.0 product (though the third digit had somewhat different semantics in
NiFi 0.x). No bug
Hi Omer,
If you're interested in some help to implement, test, or review a
graphite/grafana metrics reporter please let me know! We have written a
very simple version and are interested in getting support into the main
codebase as well.
-Andrew
On 09/17/2017 05:57 PM, Joe Witt wrote:
Omer