Hey Pierre,
You can version the metadata db in the root dir of the git repo with event
hooks.
With an h2 jdbc url of
'jdbc:h2:$NIFI_REGISTRY_HOME/database/nifi-registry-primary;AUTOCOMMIT=OFF;LOCK_MODE=3;LOCK_TIMEOUT=25000;WRITE_DELAY=0;AUTO_SERVER=TRUE'
You can connect to the db in a separate
Bryan,
Thanks for the details. On my side, the main feature I (and others I
suppose) am looking for is the ability to rebuild the metadata DB from the
Git repo. But to be honest, this is not a blocker at all: I can live with a
custom Docker image containing this feature.
So, from my point of
Ryan,
The short answer to your question is no, there isn't actually anything
new in the UI. The registry UI is setup in a generic way to list
"versioned items", so versioned extension bundles will just
automatically show up in the list with versioned flows.
Let me put together a wiki page that
Bryan,
Is there a new GUI part of the registry for the extension registry work
in master? I compiled 0.4.0-SNAPSHOT and didn't see anything immediately.
You mentioned docs and sys admin stuff... Could you point me in the
quick-start path if I wanted to try to kick-the-tires a little on this?
All,
I'm creating a 1.9.2 JIRA release now and tagging items to it. I've
updated the release page to discourage downloads of 1.9.1.
I do not plan to edit the downloads page until we have a 1.9.2 release
out. The older releases are available in the archive in case folks need
them.
Thanks
Joe
Ryan, Binlei,
Yep - I'm just getting up to speed on that PR and JIRA now. It is
certainly worthy of a 1.9.2 and once testing confirms we're good I'll
initiate an RC.
I don't intend to sweep up too many other JIRAs because I don't want to
slow down the process of getting a maintenance fix out
Our content repo (7 tb) will fill up if not restarted ever few hours, we
had to fall back to 1.8.
On Wed, Mar 27, 2019 at 10:50 AM BINLEI XUE wrote:
> Me too
>
> On Wed, Mar 27, 2019 at 10:47 PM Ryan Ward wrote:
>
> > I just came across NIFI-6150 and was wondering if there are plans to
> >
Me too
On Wed, Mar 27, 2019 at 10:47 PM Ryan Ward wrote:
> I just came across NIFI-6150 and was wondering if there are plans to
> release 1.9.2?
>
Ryan,
Let me ask about a prerequisite: why do you think 1.9.2 is going to be released
at all? __
I think the next release is going to be 1.10 unless some serious degradation is
found in 1.9.1
Regards,
Arpad
On 27/03/2019, 15:47, "Ryan Ward" wrote:
I just came across NIFI-6150 and was
I just came across NIFI-6150 and was wondering if there are plans to
release 1.9.2?
Hi Mike
Thank you for the heads up. I will check out the processors you have listed
and ensure I don't duplicate efforts. Thanks!
Chris Lundeberg
On Wed, Mar 27, 2019, 8:13 AM Mike Thomsen wrote:
> Chris,
>
> Don't know if you've created them yet, but here's a few things you might
> want
Chris,
Don't know if you've created them yet, but here's a few things you might
want to consider:
> 2. *StandardizeDate* - Reads a key/value pair from an attribute and loops
over the keys within the incoming data. If it finds a match, it will
standardize the value of that key as ISO-8601.
We
Hello NiFi Dev Team,
We are using ConsumeMQTT processor to read the messages from RabbitMQ server.
We have experienced the order on which data is passed through ConsumeMQTT
processor is different than the data order in Rabbit MQ queue.
We are working on a real time data processing pipeline,
13 matches
Mail list logo
