You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for this, I thought the biggest problem was that the root directory didn't have all the META-INF content, so I followed this approach to fix it.
Let me explain to you the current mechanism here. Currently, in order to isolate classes, we have extracted the jar into a subdirectory, which can avoid loading classes that are prone to conflicts in the default classloader. Then we use the new classloader during runtime to load the contents of the subdirectory.
The entire jar has been decompressed to a subdirectory, and a new classloader will access the entire subdirectory. This requires that the contents of the subdirectory be complete files, including META-INF. Why? For example, classes for JDk11 will be included, which cannot be deleted.
Search before asking
Paimon version
0.6.0-rc2
Compute Engine
n/a
Minimal reproduce step
unzip https://repository.apache.org/content/repositories/orgapachepaimon-1031/org/apache/paimon/paimon-s3-impl/0.6.0-incubating/paimon-s3-impl-0.6.0-incubating.jar
you'll find a nested META-INF dir
What doesn't meet your expectations?
We shouldn't include the nested META-INF dir
Anything else?
I think all of your bundle jars should be reviewed again. I have reported similar problems before.
#2424 and #2429 are incomplete fixes
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: