跳至內容

AWS glue header doesn't work properly

0

Hello. I am using aws glue, but the aws glue header does not automatically recognize it. In other words, the header is included in the data and the query does not work properly. The header is Korean, and I tried classfier, but it didn't work. Is there a solution?

plus. I use Athena to get the result.

已提問 4 年前檢視次數 1769 次

2 個答案
0

The classifier has an option to enter the column names if your columns are not dynamic. Enter image description here Enter image description here

If that would not work, you could try one of the following:

  • Change the column names in the Data Catalog, set the SchemaChangePolicy to LOG, and set the partition output configuration to InheritFromTable for future crawler runs.
    
  • Create a custom grok classifier to parse the data and assign the columns that you want.
    
AWS

已回答 4 年前

0

Hi community,   I have tried crawling a csv source, without mentioning custom classifer of 'detect headings' by default in custom. hence it was not showing proper coloumn names in the catalog.  I tried editing the existing crawler with  that custom classifier, the table refelcted was still not fixed.   so i created new crawler with that custom classfier with 'detect heading', and it worked out, i am getting proper coloumn names in table. Thankyou

已回答 2 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。