With Redis and HBase you can set a TTL on the data itself in the lookup
table. Were you thinking something more than that?
On Fri, Feb 8, 2019 at 4:42 PM Andrew Grande wrote:
> Can I suggest a time-based option for specifying the window? I think we
> only mentioned the number of records.
>
>
Can I suggest a time-based option for specifying the window? I think we
only mentioned the number of records.
Andrew
On Fri, Feb 8, 2019, 8:22 AM Mike Thomsen wrote:
> Thanks. That answers it succinctly for me. I'll build out a
> DetectDuplicateRecord processor to handle this.
>
> On Fri, Feb
The new feature is indeed amazing but we are in the same boat and based on
what've heard we do not want to risk losing flowfiles and certainly avoid
restarts of NiFi.
decided to wait for 1.9. I hope it will out pretty soon based on the
frequency of previous releases.
On Fri, Feb 8, 2019 at
Thanks. That answers it succinctly for me. I'll build out a
DetectDuplicateRecord processor to handle this.
On Fri, Feb 8, 2019 at 11:17 AM Mark Payne wrote:
> Matt,
>
> That would work if you want to select distinct records in a given FlowFIle
> but not across FlowFiles.
> PartitionRecord ->
Matt,
That would work if you want to select distinct records in a given FlowFIle but
not across FlowFiles.
PartitionRecord -> UpdateAttribute (optionally to combine multiple attributes
into one) -> DetectDuplicate
would work, but given that you expect the records to be unique generally, this
We do not. I've thought about it, but I have not had a chance to put any work
towards it. My vision of how it would work would be to
allow user to specify N number of RecordPath values as user-defined properties.
Then have those values extracted out and another
Record would be considered a
Mike,
I don't think so, but you could try a SELECT DISTINCT in QueryRecord,
might be a bit of a pain if you want to select all columns and there
are lots of them.
Alternatively you could try PartitionRecord -> QueryRecord (select *
limit 1). Neither PartitionRecord nor QueryRecord keeps state so
Do we have anything like DetectDuplicate for the Record API already? Didn't
see anything, but wanted to ask before reinventing the wheel.
Thanks,
Mike
Thinking about it more, I guess if you are not trying to do spnego
then that message from the logs is not really an error. The registry
UI always tries the spnego end-point first and if it returns the
conflict response (as the log says) then you get sent to the login
page.
Maybe try turning on
Looking forward to this fix! Thanx for all the hard work on NiFi
Regards,
Dano
On Fri, Feb 8, 2019 at 7:58 AM Mark Payne wrote:
> Chad,
>
> Upon restart, they will continue on, there is no known data loss situation.
>
> That said, we are preparing to assemble version 1.9 of NiFi now, so
Chad,
Upon restart, they will continue on, there is no known data loss situation.
That said, we are preparing to assemble version 1.9 of NiFi now, so I would
guess that it will be voted on, perhaps as early as next week. So it may (or
may not)
make sense for you, depending on your situation, to
My team is about to start using load balanced queues in 1.8 and one thing I
wanted to understand before we do is if we run into this issue and we follow
Dan’s workaround of disconnecting the node and then restarting the node node,
do the flowfiles end up moving through the rest of the flow or
Hi Bryan,
I don't have this properties populated in Nifi registry instance
outside Docker (as a service on linux server), and everything works.
What are this properties up to?
Regards,
Tom
On Fri, 8 Feb 2019 at 15:25, Bryan Bende wrote:
> The message about "Kerberos service ticket login
The message about "Kerberos service ticket login not supported by this
NiFi Registry" means that one of the following properties is not
populated:
nifi.registry.kerberos.spnego.principal=
nifi.registry.kerberos.spnego.keytab.location=
On Fri, Feb 8, 2019 at 8:20 AM Tomislav Novosel wrote:
>
>
Hi Daniel,
Ok, I see. Thanks for the answer.
I switched to official Nifi registry image. I succeeded to spin up registry
in docker container and to
setup Kerberos provider in identity-providers.xml. Also I configured
authorizers.xml as per afficial Nifi documentation.
I already have the same
Hi Tomislav,
I created that build a long time ago before the official apache one was up,
and it is out of date sorry.
Can I suggest you switch to the official apache image that Kevin mentioned
and try again? It is an up to date version and recommended by the community.
On Thu, Feb 7, 2019 at 5:54
16 matches
Mail list logo
