You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now I want to migrate my service to Hive connector catalog from AWS Glue. My data storage is AWS S3. And I use the partition projection function. In Glue, the partition key format is 'yyyy-HH-dd HH:mm:ss', and the S3 location path is '=yyyy-HH-dd-HH-mm'. But in hive catalog, the S3 path must be same to the partition. Then I cannot query data with partition 'yyyy-HH-dd HH:mm:ss'. Is there any way to keep the existing format in trinodb?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi experts,
Now I want to migrate my service to Hive connector catalog from AWS Glue. My data storage is AWS S3. And I use the partition projection function. In Glue, the partition key format is 'yyyy-HH-dd HH:mm:ss', and the S3 location path is '=yyyy-HH-dd-HH-mm'. But in hive catalog, the S3 path must be same to the partition. Then I cannot query data with partition 'yyyy-HH-dd HH:mm:ss'. Is there any way to keep the existing format in trinodb?
Thanks a lot
Beta Was this translation helpful? Give feedback.
All reactions