[ 
https://issues.apache.org/jira/browse/HUDI-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

谢波 updated HUDI-1812:
---------------------
    Description: 
Add option:
{code:java}
public static final ConfigOption<Long> INDEX_STATE_TTL = ConfigOptions
    .key("index.state.ttl")
    .longType()
    .defaultValue(24 * 60 * 60 * 1000L)
    .withDescription("index state ttl in milliseconds. default is 1 day.");
{code}
If the state expires but there are still updates for old records, the records 
would be recognized as INSERT instead of UPDATE thus some data duplication.

  was:
Add option:

{code:java}
public static final ConfigOption<Double> INDEX_STATE_TTL = ConfigOptions
      .key("index.state.ttl")
      .doubleType()
      .defaultValue(1.5D)// default 1.5 days
      .withDescription("Index state TTL in DAYs, default 1.5 days");
{code}

If the state expires but there are still updates for old records, the records 
would be recognized as INSERT instead of UPDATE thus some data duplication.



> Add explicit index state TTL option for Flink writer
> ----------------------------------------------------
>
>                 Key: HUDI-1812
>                 URL: https://issues.apache.org/jira/browse/HUDI-1812
>             Project: Apache Hudi
>          Issue Type: Improvement
>          Components: Flink Integration
>            Reporter: Danny Chen
>            Assignee: 谢波
>            Priority: Major
>             Fix For: 0.9.0
>
>
> Add option:
> {code:java}
> public static final ConfigOption<Long> INDEX_STATE_TTL = ConfigOptions
>     .key("index.state.ttl")
>     .longType()
>     .defaultValue(24 * 60 * 60 * 1000L)
>     .withDescription("index state ttl in milliseconds. default is 1 day.");
> {code}
> If the state expires but there are still updates for old records, the records 
> would be recognized as INSERT instead of UPDATE thus some data duplication.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to