You need to give the host where the NiFi instance is running in
nifi.web.http.host. For ex, say you are clustering NiFi in three nodes:
10.8.18.41, 10.8.18.42, 10.8.18.43. The nifi.properties in the respective
nodes should have the node's hostname or IP for nifi.web.http.host. You
need to
It is like Matt read my mind.
On Sat, Feb 10, 2018 at 6:26 PM, Matt Burgess wrote:
> I'm fine with a vote, but I'll be voting to keep Java as the single
> language for the (non-test) code. I share the same concerns as many of
> the other folks as far as accepting other
I'm fine with a vote, but I'll be voting to keep Java as the single
language for the (non-test) code. I share the same concerns as many of
the other folks as far as accepting other languages, it's mainly the
"slippery slope" argument that I don't want to turn into a
JVM-language flame war. If
Wasn't there a warning trigger about the NiFi distro size from Apache
recently? IMO, before talking alternative languages, solve the modularity
and NAR distribution problem. I think the implementation of a module won't
matter much then, the point being not everything has to go in the core,
base
This probably necessitates a vote, yeah?
Frankly, I’m usually happier writing Scala, and I’ve not encountered any
problems using processors written in Scala, but I think it’ll be important to
tread lightly.
There’s a few things that pop into my head:
- Maintainability and reviewability. A
Currently it means that the dataflow manager/developer is expected to
set the 'Execution Nodes' strategy to "Primary Node" at the time of
flow design.
We don't have anything that restricts the scheduling strategy of a
processor, but we probably should consider having an annotation like
Does anyone know how to cluster NiFi 1.5.0? I want to use
dataflow.mydomain.com but... I get this error when I try to hit the
loadbalancer that reads:
"The request contained an invalid host header [dataflow.mydomain.com] in
the request [/nifi/]. Check for request manipulation or third-party
I agree more with Andy about sticking with Java. The more varying languages
used, the more challenging it is to maintain. Once the code is part of the
Apache NiFi git repo, it is now the responsibility of the committers and
PMC members to maintain it.
I’d even say I am somewhat against the
+1 to Joe's response. If you can develop a component in Groovy or Scala
(or Clojure!) more quickly/comfortably, or if allowing components written
in other languages would encourage people to contribute more, I'm all for
it.
On Sat, Feb 10, 2018 at 7:42 AM Joe Witt wrote:
>
i personally would be ok with it for an extension/processor provided it
integrates well with the build.
i would agree with andys view for core framework stuff but for extensions i
think we can do it like mikethomsen suggested.
others?
thanks
joe
On Feb 10, 2018 7:30 AM, "Mike Thomsen"
I'm just a community contributor, so take that FWIW, but a compromise might
be to publish the Scala code as separate maven modules to maven central and
then submit a thoroughly tested processor written in Java. As long as you
have enough unit and integration tests to give strong coverage, I
11 matches
Mail list logo