It worked!
I had to actually delete the Processor and add a new new. Stopping and
starting the Processor or the Flow didn't actually work.
Thanks,
Pablo.
On Wed, Oct 26, 2016 at 3:59 PM, James Wing wrote:
> Pablo,
>
> Did you by any chance start the GetDynamoDB processor
Pablo,
Did you by any chance start the GetDynamoDB processor first without the
credentials, then stop, configure credentials, and restart? I suspect
there might be a bug where GetDynamoDB caches the client even through
stopping and starting the processor.
To test this theory, you might try
Hi,
I've been trying to get GetDynamoDB processor to work. I've configured the
AccessKey and SecretKey but i'm still getting Exception
*MissingAuthenticationTokenException*. Any ideas?
This is the Error from the Bulletin Board.
GetDynamoDB[id=f14db94a-0157-1000-4a66-5f7d9437a744] Could not
Johny,
What version of NiFi are you using? Also are you trying to get
documents from ES using FetchElasticSearch(Http) or put docs to it
using PutElasticsearch(Http)? For Fetching, the Document Identifier
is the _id of the document you want to retrieve. If you're looking to
do a search on
Hello,
Do you guys have an example config of how this processor should look? I
have a regular easticsearch install that is only receiving syslogs. I'm
trying to figure out how to find or what to put for document identifier. I
did a curl in elasticsearch and saw a field "id" but, it does not look
Alessio
It just isn't supported yet as that was never a case that was needed.
Folks would like it now. So it is a new feature or enhancement rather
than a bug.
It is fine to increase the priority of it. I just bumped it major.
In either case the key now is to join the discussion as needed to
I see on https://issues.apache.org/jira/browse/NIFI-401:
priority : Minor
Type: Improvement
Are we sure about this ?
I think this is a priority bug.
Is it just me who is facing the problem to start ONE flowfile into the
cluster?
On 24/10/2016 15:01, Joe Witt wrote:
> Alessio,
>
> We don't