-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Querying partitioned S3 data source error #24840
Comments
Could you share the full stacktrace? You can get it with CLI debug option or Web UI. |
@ebyhr as requested:
|
I think setting |
@raunaqmorarka
Worked. I assume this has a performance hit, so I'll look at using the alternative library you suggest. The documentation for it is very poor however. Thanks for your help. |
Parquet column indexes don't help on most queries, they help a little bit on needle-in-a-haystack style queries |
I have some parquet files in s3 in partitions: year=, month=day=, e.g.
bucket1/year=2025/month=01/day=01/metrics.parquet
bucket1/year=2025/month=01/day=02/metrics.parquet
I can retrieve the whole data set with 'select * from <table_name> but as soon as I try to add a where clause either on the partition value or some value in the data, I get errors.
Here's my setup:
NB. Trino ops against RDS have no problem.
Hive has an IAM user that is able to operate on the target S3 bucket. IAM user has following policy (some details changed for security)
The user that is being used to log into Trino, has a set of catalogs they can see, determined by a file based ACL. The user also has an associated IAM profile, and their IAM keys etc are stored as part of the catalog description. The IAM user has an associated role that allows
My catalog is defined as (mycat.properties)
My schema is defined as:
The table creation statement is:
Finally, I call:
If I do a simple
select * from daily limit 10;
I get a result.If I do
select * from daily where namespace = 'da-incident-etl.load' and day=28 limit 10;
I get an error:I'd really appreciate some help here. It's taken months to get this set up and this is kind of the final stumbling block to full adoption of Trino.
Trino V 449
Any help appreciated.
Ashley
I have tried this with the parquet file being compressed and uncompressed
The text was updated successfully, but these errors were encountered: