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
Describe the bug
A clear and concise description of what the bug is.
The Tap has no functionality to handle junk characters/special characters in headers ( that is not visible to naked eyes) . Also it doesn't remove spaces in between headers ("column name" -> column_name) to make it more suitable for databases and it doesn't remove the trailing white spaces in headers. These all are very crucial since some third-party apps exports there data directly to s3 and we don't have much say in controlling the headers. and as per the standard column names should not contain spaces or special character.
To Reproduce
Steps to reproduce the behavior:
Prepare the data as '...' put non-ascii values or junk values in colunm name for example "\ufeffmessage_id" and try to load it with passing key_properties as ["message_id"], it will fail since it would not be able to find message_id
Run the command '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
if the column has special character, it should be removed and spaces should be replaced with _,
ex: "\ufeffmessage_id" -> "message_id"
"message id" -> "message_id"
message%%id-> message_id Screenshots
If applicable, add screenshots to help explain your problem.
Your environment
Version of tap: [e.g. 2.0.0]
Version of python [e.g. 3.8]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
The Tap has no functionality to handle junk characters/special characters in headers ( that is not visible to naked eyes) . Also it doesn't remove spaces in between headers ("column name" -> column_name) to make it more suitable for databases and it doesn't remove the trailing white spaces in headers. These all are very crucial since some third-party apps exports there data directly to s3 and we don't have much say in controlling the headers. and as per the standard column names should not contain spaces or special character.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
if the column has special character, it should be removed and spaces should be replaced with _,
ex: "\ufeffmessage_id" -> "message_id"
"message id" -> "message_id"
message%%id-> message_id
Screenshots
If applicable, add screenshots to help explain your problem.
Your environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: