Hello,
If you'd like to load data from CSV file to database table, 1.2.0 also
has PutDatabaseRecord processor.
Then you can configure PutDatabaseRecord to use CSVReader. Since you
have your schema within incoming file as CSV header, no need to setup
Schema Registry.
However, "random number of
Glad to have you joining the PMC Yolanda, very well deserved!
On Thu, May 18, 2017 at 12:02 AM, Jeff wrote:
> Congrats Yolanda!
>
> On Wed, May 17, 2017 at 10:43 PM Yolanda Davis
> wrote:
>
> > Thank you everyone! It has been my pleasure to
Congrats Yolanda!
On Wed, May 17, 2017 at 10:43 PM Yolanda Davis
wrote:
> Thank you everyone! It has been my pleasure to continue to contribute to
> and support this awesome community. Definitely looking forward to all the
> great things ahead!
>
> On Wed, May 17,
Thank you everyone! It has been my pleasure to continue to contribute to
and support this awesome community. Definitely looking forward to all the
great things ahead!
On Wed, May 17, 2017 at 10:32 PM, Koji Kawamura
wrote:
> Congratulations Yolanda, well deserved! I have
Congratulations Yolanda, well deserved! I have a great respect for
your excellent work.
On Thu, May 18, 2017 at 11:15 AM, Andy LoPresto wrote:
> Congratulations Yolanda. Well deserved and very excited for your continued
> excellent contributions to all aspects of the
Congratulations Yolanda. Well deserved and very excited for your continued
excellent contributions to all aspects of the project.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On May 17, 2017, at 7:14 PM, Joe
Agree very much with Tony's excellent writeup.
Congrats and thank you Yolanda!
On Wed, May 17, 2017 at 10:11 PM, Tony Kurc wrote:
> On behalf of the Apache NiFi PMC, I am pleased to announce that Yolanda
> Davis has accepted the PMC's invitation to join the Apache NiFi PMC.
On behalf of the Apache NiFi PMC, I am pleased to announce that Yolanda
Davis has accepted the PMC's invitation to join the Apache NiFi PMC. We
greatly appreciate all of Yolanda's hard work and generous contributions to
the project. We look forward to continued involvement in the project.
I know
Apache NiFi Community,
I am pleased to announce that the 0.7.3 release of Apache NiFi passes with
5 +1 (binding) votes
0 -1 (binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible!
Here is the PMC vote thread:
+1 (non-binding)
Verified signatures
Verified hashes
Built cleanly using contrib check
Built simple flow to communicate with NiFi 1.2
converted flow with toolkit
ran flow
Verified flowStatus JSON
On Wed, May 17, 2017 at 4:18 PM, Tony Kurc wrote:
> +1 (binding)
>
> -
+1 (binding)
- verified signatures
- verified hashes
- build cleanly
- verified a simple flow
- I think c2 worked as expected
- ran toolkit's config.sh and did some converting without issue
On Mon, May 15, 2017 at 12:55 PM, Aldrin Piri wrote:
> Hello,
>
> I am pleased to be
+1 (binding)
Release this package as nifi-0.7.3.
Thanks!
Matt
On Sun, May 14, 2017 at 8:33 PM, Michael Moser wrote:
> Hello Apache NiFi community,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi nifi-0.7.3.
>
> The source zip, including
+1 (binding)
Verified all downloads, checksums, and signature.
Verified README, LICENSE, and NOTICE present.
Ran a flow with MiNiFi getting files and sending to NiFi over S2S.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B
+1 (binding)
Release this package as minifi-0.2.0
Thanks!
Matt
On Mon, May 15, 2017 at 12:55 PM, Aldrin Piri wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> MiNiFi, minifi-0.2.0.
>
> The source zip, including signatures,
+1 (binding)
Verified all the usual suspects. Checked the now disallowed json.org
dependency is not present. Verified it works in a flow (hadnt seen
this version in a long time).
Thanks for pulling together.
On Tue, May 16, 2017 at 5:24 PM, James Wing wrote:
> +1 (binding),
I assigned NIFI-479 to myself and will work on it. Definitely a cool feature
to highlight in the docs!
-Drew
> On May 17, 2017, at 1:26 PM, Michael Moser wrote:
>
> I was going to add a JIRA to add this to the Developer's Guide, but I
> see [1] one already exists.
>
>
+1 (binding) Release this package as minifi-0.2.0
Verified signatures and hashes, ran full build with contrib-check,
verified licenses/notices in all binaries, and ran sample flow from
MiNiFi to NiFi.
On Wed, May 17, 2017 at 11:38 AM, Pierre Villard
wrote:
> +1
I was going to add a JIRA to add this to the Developer's Guide, but I
see [1] one already exists.
-- Mike
[1] - https://issues.apache.org/jira/browse/NIFI-479
On Wed, May 17, 2017 at 1:18 PM, Joe Witt wrote:
> wow - i think i need to learn more about this NiFi thing. That
wow - i think i need to learn more about this NiFi thing. That is awesome!
On Wed, May 17, 2017 at 1:15 PM, Matt Gilman wrote:
> I just wanted to clarify that additional content viewers can be added to
> existing builds without internal changes or a custom NiFi build.
I just wanted to clarify that additional content viewers can be added to
existing builds without internal changes or a custom NiFi build. Content
viewers (and Custom UIs) are discovered at start up in a similar to how
Processors are discovered. A content viewer can be bundled in any NAR and
each
Thanks Joe.
For community:
You did bring up a good point about external viewer and what we actually
ended up doing was run a subset of the mime.type to and ExecuteStream
processor that could convert it to text and then we UpdateAttribute to
mime.type = text/plain > Then auto terminate success.
+1 non-binding
Signature, checksums, license, readme.
Full build with contrib check - basic flows tested.
Pierre
2017-05-17 15:37 GMT+02:00 Bryan Rosander :
> +1 non-binding
>
> Verified signature, checkums
> Ran build with docker and contrib-check (mvn -P docker -P
At present it is not designed as a clearly API separated extension
point like processors or controller services and the like. It might
make more sense to enable integration to an external viewer
service/capability than to make it a first class extension point.
But, for now, it requires internal
+1 non-binding
Verified signature, checkums
Ran build with docker and contrib-check (mvn -P docker -P contrib-check
clean install) and empty m2 folder
Set up c2 docker-compose configuration with a delegating c2 server,
authoritative c2 server pointing at nifi cluster, 5 minifi nodes
Tested a
Good morning,
How involved is it to add an additional content viewer for a mime type?
Our quick preliminary research leads us to modifying a few pieces of
framework.
Is this right path? Has anyone been able to add an additional mime type to
be viewed under provenance "view" function?
Thank
I have implemented solution of creation flow files and working perfectly only
problem I am facing is flow files are transferred after completion of
processor or on commit of session. Is there any way i send flow files as it
is generated to the next processor if i commit session after a
Hi All,
I am using nifi version 1.2.0.
We have CSV files given by Vendor with random number of Columns in the file.
We want to save the contents of the File in Postgres Database.
I have created a Flow with the following processors.
GetFile-->ConvertRecord-->ConvertJSONToSql--->PutSql
In
27 matches
Mail list logo