Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Table optimization skipped due to configuration parsing error #2656

Open
2 tasks done
XBaith opened this issue Mar 20, 2024 · 0 comments · May be fixed by #2657
Open
2 tasks done

[Bug]: Table optimization skipped due to configuration parsing error #2656

XBaith opened this issue Mar 20, 2024 · 0 comments · May be fixed by #2657
Labels
type:bug Something isn't working

Comments

@XBaith
Copy link
Contributor

XBaith commented Mar 20, 2024

What happened?

Set a retention time with unsupport time unit in data expire configuation, AMS throws the IllegalArgumentException when load/refresh the TableRuntime. Therefore table cannot be optimized

Affects Versions

master/0.6.x

What engines are you seeing the problem on?

AMS

How to reproduce

  1. start AMS
  2. set illegal retention time, such as '13m'
  3. enable data-expiring

Relevant log output

No response

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

  • I agree to follow this project's Code of Conduct
@XBaith XBaith added the type:bug Something isn't working label Mar 20, 2024
@XBaith XBaith linked a pull request Mar 20, 2024 that will close this issue
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[AMORO-2656] Enhance TimeUtils and fix config parsing error XBaith/amoro
1 participant
@XBaith