Good to know. Is there a way to disable this? I have some queries when I just would like to know the outcome of the query for ETL and I do not need anything else. Not sure if that is doable with Athena.
The Life Cycle transition is brilliant. The simple lambda interesting, too. Combine both with S3 object versioning to open a door!
Combining Life Cycles and object versioning can also reduce costs. Object versioning is a game changer. Two versions of a single query result may be stored with S3 object versioning. Each object with different attributes. The first object is the Athena generated object with a transition to a lower cost tier. Example: a csv and glacier. The second object could be the compressed version of the exact same object, at a more available S3 tier. Example: compressed at standard tier. Each version has a different version id. Create the compressed version automatically. Configure S3 to send an event when a query result is put in the bucket and trigger a lambda to compress the file and put the compressed file in the bucket as a second version of the query result. Combining life cycling and versioning is like opening up a door.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good to know. Is there a way to disable this? I have some queries when I just would like to know the outcome of the query for ETL and I do not need anything else. Not sure if that is doable with Athena.
I don't think it's possible to disable it. One solution would be to have a simple Lambda function to clean your files after a few minutes.
The Life Cycle transition is brilliant. The simple lambda interesting, too. Combine both with S3 object versioning to open a door!
Combining Life Cycles and object versioning can also reduce costs. Object versioning is a game changer. Two versions of a single query result may be stored with S3 object versioning. Each object with different attributes. The first object is the Athena generated object with a transition to a lower cost tier. Example: a csv and glacier. The second object could be the compressed version of the exact same object, at a more available S3 tier. Example: compressed at standard tier. Each version has a different version id. Create the compressed version automatically. Configure S3 to send an event when a query result is put in the bucket and trigger a lambda to compress the file and put the compressed file in the bucket as a second version of the query result. Combining life cycling and versioning is like opening up a door.