There's no state currently, ie state is empty. I would think that when there's no state, ListS3 would start from the beginning?
FYI, the only items I've filled in in the ListS3 processor are: - Bucket: Our bucketname. - Region: Apparently I have to choose one, this is set to us-west-2 - Access Key: <set> - Secret Key: <set> I'm pretty sure the above settings are correct because when I do "aws s3 ls s3://<bucketname>" with the above keys, I do get output. On 2017-07-20 09:18, Pierre Villard wrote: > Can you check what's the current state of the processor? (right click / view > state) Are you sure there is data to retrieve more recent that what is > currently in the processor's state? > > Pierre > > 2017-07-20 18:16 GMT+02:00 Laurens Vets <laur...@daemon.be>: > > I'm running 1.3.0 at the moment... I'm tempted to go back to 1.2.0 as I > remember I got something working with S3. > > Can I just downgrade? > > On 2017-07-20 09:12, Adam Lamar wrote: > Hi Laurens, > > What NiFi version are you running? There was an issue where ListS3 would spin > like that on buckets with many files, but it was fixed in version 1.1.0 IIRC. > > Hope that helps, > Adam > > On Thu, Jul 20, 2017 at 10:05 AM, Laurens Vets <laur...@daemon.be> wrote: > Hello, > > I'm trying to ingest AWS CloudTrail logs with NiFi. I think I configured > ListS3 correctly, but it has been running for hours & hours without showing > anything (except for the # of tasks). > > How long does it take before I should see _any_ output/state/something in the > ListS3 processor?
