csurong opened a new issue, #11002:
URL: https://github.com/apache/paimon/issues/11002

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/paimon/issues) 
and found nothing similar.
   
   
   ### Paimon version
   
   master at e1e1bf705e1a5a81cb1466238678afab5c97cdd3.
   
   ### Compute Engine
   
   Flink expire_partitions action. Verified with the flink1 Maven profile.
   
   ### Minimal reproduce step
   
   1. Configure a partitioned table with `'partition.expiration-strategy' = 
'update-time'`.
   2. Write data to a partition named `dt=2020-01-01`.
   3. Immediately run the Flink `expire_partitions` action with the following 
arguments, without `--expire_strategy`:
   
   ```text
   --expiration_time '7 d'
   --timestamp_formatter 'yyyy-MM-dd'
   ```
   
   The action expires the partition based on its date value, even though it was 
just written. Passing `--expire_strategy update-time` explicitly retains the 
partition.
   
   ### What doesn't meet your expectations?
   
   When an optional action argument is omitted, the action should inherit the 
corresponding table option, including overrides supplied through 
`--table_conf`. Explicit action arguments should take precedence.
   
   Currently, omitting `--expire_strategy` falls back to `values-time`, even if 
the table uses `update-time`. In the example above, the recently written 
partition should be retained because its update time is within the seven-day 
retention period.
   
   Similarly, omitting `--timestamp_pattern` uses the first partition field 
instead of the configured `partition.timestamp-pattern`. Overrides supplied 
through `--table_conf` are also ignored for these options.
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


-- 
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