-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] [connectors] elasticsearch Index not supports field name variables #8390
Comments
@FuYouJ here |
If it is a dynamic index, please try schema_save_mode="IGNORE" @zhdech |
|
This may not be a bug, it is configured in this way. If it is not a dynamic index, it is necessary to manipulate the table through schema_save_mode, which includes RECREATE_SCHEMA, CREATE_SCHEMA_WHEN_NOT_EXIST,ERROR_WHEN_SCHEMA_NOT_EXIST,IGNORE, And these operations all occur before the synchronization task, which can be viewed in the document https://seatunnel.apache.org/docs/connector-v2/sink/Elasticsearch/ |
两个问题: |
1,The document does have some issues and needs to be improved |
If dynamic indexing is used, it is not supported to create a table when it does not exist by setting schema_save_mode to CREATE-SCHEMA_CHEN_NOT_deIST.The index or field is dynamically created during actual use |
Tables created with CREATE_SCHEMA_WHEN_NOT_EXIST are created by SeaTunnel, while dynamic indices are created by ES itself, so IGNORE needs to be configured. |
Okay, I understand. Thank you |
Search before asking
What happened
When writing ES, the dynamic index [seatun_ ${age}] cannot be used, and this field must appear in the seatunRow. If not, we will consider it as a regular index
After debugging, I should first replace the variables and then verify if the index is correct; But now the code logic is reversed, causing some variables to report errors (unable to enter replacement logic)
写ES时,无法使用动态索引【 seatunnel_${age},并且该字段必须出现在 seatunnel Row 中。如果没有,我们将把它视为普通索引】
debug了下,应该是先替换变量,然后在验证索引是否正确;但是现在代码逻辑反了,导致有变量是报错(无法进入到替换逻辑)
SeaTunnel Version
2.3.8



SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: