Mark,
This echoes if not answers a concern I've had with the whole concept of
backing up the repositories.
Second, our users have just about completely shut provenance down as not
useful enough to justify the disk space and crunch (in a desperate,
vague expression of "throw everything non-es
Is there a nifi processor that will output a bunch of flowfile attributes
as delimited text (i.e. csv)? I had checked google a while ago and the
suggestion was to use ReplaceText. The problem with this is that we have to
add all the field delimiters, quotes and escaping of characters to each
attrib
Russ,
Given that the Content & FlowFile Repositories are intended to be rather
short-lived,
I'm not sure that you'd really have need to backup the repository (if you were
to pause the flow
in order to back it up, for instance, you could likely process the data just as
fast as you could
back
Been Googling hard on this (NiFi docs, Horton docs, these forums,
stackoverflow) and I'm not seeing anything about specific wisdom
surrounding backing up /content_repository/ and /flowfile_repository/,
why I would, why I wouldn't, turning NiFi off when I do, etc.
I completely get the rest of t
