Mike,
I don’t believe there are any APIs to perform that action. You could likely
achieve it by using an ExecuteStreamCommand processor and invoking “rm -rf
/path/to/flowfile_repository” but I’m not sure if that would cause an issue
given the triggering flowfile being executed at the time.
Hi Andrew,
I was wondering if you got the chance to review the information i sent. I
seem to have tried most of the options but i guess Nifi doesn't scale by
default much like other distributed systems that i have worked with (mainly
teradata) and needs to be configured alot before you can expect
Are there any APIs that could be leveraged internally be a "reset"
processor to tell the flow file repository to purge everything?
Thanks,
Mike
Also, start planning to remodel your data if you're using more than one
type per index because they're phasing out types as well. If you have
existing indexes that use two or more types and try to rebuild them the
same way with ES 6 it's not going to allow that either.
JsonQueryElasticSearch
Hello all,
I am getting unexpected behavior while using QueryElasticSearchHttp into an
ES 6 instance.
Does NIFI support ES 6?
I can send it documents but when I query it I ingest my flowfile instead of
getting a result back.
At this point, I am not sure if I am just using the processor wrong or
