Hi, I'm wondering if the people that use Drill with S3 are using some sort of local cache on the drillbit-nodes for historical, non changing, Parquet segments.
I'm pretty sure that I'm not using the correct terminology and that the correct question is this: Are there any ways to optimize S3 with drill so that "hot segments" are stored locally while hot and then just dropped from local nodes when they are not. I guess this only really matters where networking speeds between the drill-bit nodes and S3 is not optimal. Regards, -Stefan