[
https://issues.apache.org/jira/browse/FLINK-24571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456487#comment-17456487
]
Martijn Visser edited comment on FLINK-24571 at 12/9/21, 2:56 PM:
------------------------------------------------------------------
CC [~alexanderpreuss] - Perhaps it's good to also look at this PR since you're
working on the Elasticsearch connector
Edit: I see that you're already reviewing, sorry :)
was (Author: martijnvisser):
CC [~alexanderpreuss] - Perhaps it's good to also look at this PR since you're
working on the Elasticsearch connector
> elasticsearch dynamic index support the use of proctime
> --------------------------------------------------------
>
> Key: FLINK-24571
> URL: https://issues.apache.org/jira/browse/FLINK-24571
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / ElasticSearch
> Reporter: jinfeng
> Assignee: jinfeng
> Priority: Major
> Labels: pull-request-available
>
> When use eleasticsearch dynamic index, we must special a field. If there is
> no time-attribute field, we can't use dynamic index. so support dynamic
> index using proctime may be a good choice.
> Before implement this feature, we should discuss the proctime index pattern.
>
> The current dynamic index is :
> {code:sql}
> Create table esSink (
> f1 timestamp(3)
> ) with (
> 'index' = 'myusers_{f1|yyyy-MM-dd}'
> );
> {code}
> When using proctime as dynamic index, It would be like this.
> {code:sql}
> Create table esSink (
> f1 varchar
> ) with (
> 'index' = 'myusers_{|yyyy-MM-dd}'
> );
> {code}
> When field name is not specified, we use proctime to generate the dynamic
> index.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
