Hi - I’m wondering if anyone has tried to read a filegeodb straight from s3 with a featurereader. The S3 connector documentation implies this might be possible - but I could not get it to work. I had to have the gdb directory local on my machine for it to work. Has anyone else run into this? It would be cool if it did work, since I don’t like having these file geodbs local. I can work around it if not.
Solved
Reading a FileGeoDB from s3
+1- Participant
Best answer by hkingsbury
You can use the TempPathnameCreator to create a temporary directory that only exists for the duration of the FME process (it gets deleted once the workbench has run).
Use this to specify the location the S3Connector downloads to and the FeatureReader reads from
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+65- Celebrity
- Best Answer
You can use the TempPathnameCreator to create a temporary directory that only exists for the duration of the FME process (it gets deleted once the workbench has run).
Use this to specify the location the S3Connector downloads to and the FeatureReader reads from
