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.

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

[Bug] when upgrade 2.3.5 version from 2.3.4, job restore failed #6853

Open
2 of 3 tasks
liunaijie opened this issue May 14, 2024 · 3 comments
Open
2 of 3 tasks

[Bug] when upgrade 2.3.5 version from 2.3.4, job restore failed #6853

liunaijie opened this issue May 14, 2024 · 3 comments
Labels

Comments

@liunaijie
Copy link
Contributor

liunaijie commented May 14, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

In version 2.3.4, i enable the IMAP storage cache, when upgrade to version 2.3.5. Will get exception when read data from the cached imap data.
the error reason is this pr https://github.com/apache/seatunnel/pull/6666/files#r1598217272 update the field type in IMAP cached class.

SeaTunnel Version

2.3.5

SeaTunnel Config

na

Running Command

na

Error Exception

image

Zeta or Flink or Spark Version

zeta

Java or Scala Version

No response

Screenshots

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@Hisoka-X
Copy link
Member

cc @EricJoy2048

@liunaijie
Copy link
Contributor Author

For the storage info (imap, checkpoint), In feature maybe still has some change, like add a filed, data type change.
We need make sure we can compatible with old version (at least last version), then we can restore the historary data.

What can we do now:

  1. fix in release version or give advice (soluaction/warning) to user that want upgrade to version 2.3.5
  2. add ut to make sure in feature when we modify those class, we can notice this case.

@Hisoka-X
Copy link
Member

add ut to make sure in feature when we modify those class, we can notice this case.

Yes, this is one I really think SeaTunnel should have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants