You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2021/10/18 03:50:00 UTC
[jira] [Comment Edited] (FLINK-24571) elasticsearch dynamic index
support the use of proctime
[ https://issues.apache.org/jira/browse/FLINK-24571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429804#comment-17429804 ]
Jark Wu edited comment on FLINK-24571 at 10/18/21, 3:49 AM:
------------------------------------------------------------
This is not very intuitive, I would suggest to use pattern
{code}
'index' = 'myusers_{now()|yyyy-mm-dd}'
{code}
was (Author: jark):
This is not very intuitive, I would suggest to use pattern {{'index' = 'myusers_{now()|yyyy-mm-dd}'}}.
> 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
> Priority: Major
>
> 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.3.4#803005)