Bug Report: AWS Glue Service - Table Name Space Issue
When creating a table with a leading space in the name, AWS Glue does not display any error during the creation process. However, upon checking the API logs, I noticed that the space is present in the actual table name, causing inconsistencies and unexpected behavior.
The problem becomes more evident when using the Glue data in conjunction with other AWS services. For instance, in one of my Firehose setups, where I intended to utilize the Glue data, an error occurred. The error message indicated that the table name did not match the expected regex, despite the fact that the space was not visible on the screen.
To provide clarity and assist in resolving this issue, I have attached screenshots illustrating the discrepancy between the displayed table name and the actual name present in the API logs.
- Newest
- Most votes
- Most comments
Technically it's legal and Glue allows it to be "hive compatible", but it would be a really bad practice and it's like to cause issues, just avoid doing that.
Relevant content
- asked 8 months ago
- asked 2 years ago
- asked 7 months ago
AWS OFFICIALUpdated 2 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hi, I cannot see your screenshots. Does this occur only when creating a table through the Glue console? Does creating a table from the AWS CLI have the same side-effects? Are you able to correct the issue by renaming the table?
I would like to replicate this issue and see if it's an issue in my AWS account as well. If so, it would be better to escalate this directly with the Glue service team as a bug instead of a post here.
when I create a table from the AWS console it doesn't give an error while creating a table with a table name having a leading space. But when I try to attach table with any aws service it gives me an error like regex match failed.