boneanxs commented on issue #4474:
URL: https://github.com/apache/hudi/issues/4474#issuecomment-1005478353
Looks flink-bundle already remove
this...[HUDI-2803](https://issues.apache.org/jira/browse/HUDI-2803)
--
This is an automated message from the Apache Git Service.
To respond to the
boneanxs commented on issue #4474:
URL: https://github.com/apache/hudi/issues/4474#issuecomment-1004795295
After some investigation about this, I'm curious why flink remove amazonaws
packages by this JIRA(it doesn't have too much description):
boneanxs commented on issue #4474:
URL: https://github.com/apache/hudi/issues/4474#issuecomment-1004507464
@xushiyan @zhedoubushishi , Looks this is a common case for many users, does
shade this has other side effects or not? If not, I'm willing to raise a ticket
to solve this.
--
This
boneanxs commented on issue #4474:
URL: https://github.com/apache/hudi/issues/4474#issuecomment-1002890635
> Error in query: Specified schema in create table statement is not equal to
the table schema.You should not specify the schema for an exist table:
`default`.`hudi_mor_s32`
boneanxs commented on issue #4474:
URL: https://github.com/apache/hudi/issues/4474#issuecomment-1002859639
For our internal hudi version, we shade aws dependencies, you can add new
relocation and build a new bundle package:
For example, to shade aws dependencies in spark, add