Robert,
I want to clarify something here:
> RC 2 is the candidate which was released, so your version is effectively 1.9.2
On a technical level this is true, but even if you have been
authorized to deploy 1.9.2 that authorization would not extend to RC2.
In such a case, it would be advisable to
Jim,
It would be helpful to understand what your use cases are with BizTalk
first. It's always difficult to compare products that are in similar,
but not same, categories like rules engines vs data orchestration
tools.
I think as a starting point, NiFi is probably the world leader at this
point
Nissim,
Thanks a lot for your contribution but there are 277 pull requests opened
at this time. This is a community effort, and if you expect people to
review your PRs, you'd have to also try reviewing PRs opened by others in
the community. Otherwise this will need to wait for someone with some
Second attempt...
Hello NiFi team,
Could someone respond to this email.
Thanks,
Nissim Shiman
On Monday, October 5, 2020, 11:01:57 AM EDT, Nissim Shiman
wrote:
Hello NiFi team,
Could someone review the pull request for NIFI-7738
(https://issues.apache.org/jira/browse/NIFI-7738),
Hey all
I work for a company that uses Biztalk extensively for Dataflow, ETL,
Application integration
We are looking a Nifi as a Business rule engine,
I am looking for supporting documentation that shows this would be a good idea,
VS using Biztalk Business rule engine
Any direction on this
Hi Robert,
The “-RC2” part of the version number indicates the release candidate of the
version. In this case, RC 2 is the candidate which was released, so your
version is effectively 1.9.2. The documentation hosted on our website changes
for the main guides with each version, but previous
CLASSIFICATION: UNCLASSIFIED
Good Afternoon,
My version of Apache NIFI is version 1.9.2-RC2
I cannot find a user/admin document for that version. Is it possible for you
to send me a PDF copy? I am new to using NIFI and I am getting configuration
errors that I cannot fix. Thanks in
Paul,
Although the description may not be the same, I think you might be
running into NIFI-7240 [1]. That Jira mentions triggers but I think
the same would occur any time you can have TABLE MAP events "out of
order". I have a PR up to solve this issue, hopefully a committer can
review and get it
HI, Team
I think it should be a bug. Could you plan to fix it or could I register a bug
for it?
The wrong issue can be reproduce with 1.9.*, 1.11.4 of NIFI version.
The mysql version is 5.7.20-log MySQL Community Server (GPL)
Wrong behavior cause by TABLE_MAP event just got the last one table is
