Closed
Bug 1558908
Opened 6 years ago
Closed 6 years ago
Error querying longitudinal v20190608: Access Denied
Categories
(Data Platform and Tools Graveyard :: Operations, defect)
Data Platform and Tools Graveyard
Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: robert.strong.bugs, Unassigned)
Details
java.io.FileNotFoundException: No such file or directory 's3://telemetry-parquet/longitudinal/v20190608/4ebcc3b0-26e4-4ac5-867b-90abe5844fae'
Comment 1•6 years ago
|
||
Hmmm
$ aws s3 ls s3://telemetry-parquet/longitudinal/v20190608/4ebcc3b0-26e4-4ac5-867b-90abe5844fae
2019-06-09 01:29:01 1372625267 4ebcc3b0-26e4-4ac5-867b-90abe5844fae
Frank do you know why this might not be visible from a Spark cluster?
Flags: needinfo?(fbertsch)
Comment 2•6 years ago
|
||
AFAICT this is a permissions issue:
Error running query: Error opening Hive split s3://telemetry-parquet/longitudinal/v20190608/4ebcc3b0-26e4-4ac5-867b-90abe5844fae (offset=0, length=67108864): com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: B0A0D40C5CE470F9; S3 Extended Request ID: geaOoUdK1elX2A4x6fwZ9+juicdwD59QoPQ/fxcm6jiQZy9dKNzNTMCoKWPa75mN5SeAwOQ0yDg=), S3 Extended Request ID: geaOoUdK1elX2A4x6fwZ9+juicdwD59QoPQ/fxcm6jiQZy9dKNzNTMCoKWPa75mN5SeAwOQ0yDg= (Path: s3://telemetry-parquet/longitudinal/v20190608/4ebcc3b0-26e4-4ac5-867b-90abe5844fae)
Can someone from ops look into this?
Component: Datasets: Longitudinal → Operations
Flags: needinfo?(fbertsch)
QA Contact: moconnor
Summary: Error querying longitudinal v20190608 → Error querying longitudinal v20190608: Access Denied
Comment 3•6 years ago
|
||
:robotblake fixed this up last night. I checked via Databricks and I can now read that file in particular.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
![]() |
Reporter | |
Comment 4•6 years ago
|
||
Thanks! It is working for me now as well.
Updated•2 years ago
|
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•