liunaijie commented on PR #6842:
URL: https://github.com/apache/seatunnel/pull/6842#issuecomment-2153773181

   > > > > partition
   > > > > 
![image](https://private-user-images.githubusercontent.com/73467479/332693557-776b220b-3ad7-4007-93be-964be5445b48.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTYzNjQ3NDgsIm5iZiI6MTcxNjM2NDQ0OCwicGF0aCI6Ii83MzQ2NzQ3OS8zMzI2OTM1NTctNzc2YjIyMGItM2FkNy00MDA3LTkzYmUtOTY0YmU1NDQ1YjQ4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA1MjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTIyVDA3NTQwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc1ODk4NDZjYmFmNWI4MmU4ZDI5Njc2MmE0NDE2MWU1NzkyMzFjM2E2M2I1OWY1ZWZlNWZiY2Y0N2MzN2JkMDMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.E9kQl0K9YYtrKM2-JA6douXQ7uj3i2jWBk9zkgMrhbw)
   > > > 
   > > > 
   > > > > > 大佬你好,创建的statement好像有点问题 
org.apache.hadoop.hive.ql.parse.ParseException:line 1:0 cannot recognize input 
near '' '' ''
   > > > > 
   > > > > 
   > > > > 是提交partition信息的语句吗 还是哪个语句?
   > > > 
   > > > 
   > > > > > 大佬你好,创建的statement好像有点问题 
org.apache.hadoop.hive.ql.parse.ParseException:line 1:0 cannot recognize input 
near '' '' ''
   > > > > 
   > > > > 
   > > > > 是提交partition信息的语句吗 还是哪个语句?
   > > > 
   > > > 
   > > > 是的,当schema_save_mode = 
"CREATE_SCHEMA_WHEN_NOT_EXIST"时,save_mode_create_template 是必须的吗?当为 “” 
时,报错为我描述的那个错误
   > > 
   > > 
   > > 是必须的, 这个是你表不存在时的要执行的建表语句
   > 
   > 那如果我不知道source的表结构的话,是否该source-sink的conf就不能成立?这个和mysql的schema_save_mode 
的配置实现的效果不一样吗?
   
   代码更新了一版, 可以在不知道上游表结构的情况下, 使用变量的形式 运行时替换掉. 
   有一点需要注意的是 如果存在分区, 则需要添加额外的参数标明分区字段, 并且分区字段不能变量化, 即多张上游表只能用一个模板内的分区定义, 
不能针对每个表建不同的分区.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to