ysmintor opened a new issue, #10937:
URL: https://github.com/apache/hudi/issues/10937

   **_Tips before filing an issue_**
   
   - Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)?
   
   - Join the mailing list to engage in conversations and get faster support at 
[email protected].
   
   - If you have triaged this as a bug, then file an 
[issue](https://issues.apache.org/jira/projects/HUDI/issues) directly.
   
   **Describe the problem you faced**
   Apache Kyuubi with Flink need flink-table-planner-loader(which is deault in 
Flink /lib), However, Hudi api depends flink-table-planner_2.12. 
   A clear and concise description of the problem. 
   There is another guy who suffer the two jar conflict problem. Is there any 
chance to move on flink-table-planner-loader.jar ?
   
   **To Reproduce**
   
https://nightlies.apache.org/flink/flink-docs-master/docs/dev/configuration/advanced/#table-planner-and-table-planner-loader
   > In the upcoming Flink versions, we will stop shipping the 
flink-table-planner_2.12 artifact in the Flink distribution. We strongly 
suggest migrating your jobs and your custom connectors/formats to work with the 
API modules, without relying on planner internals. If you need some 
functionality from the planner, which is currently not exposed through the API 
modules, please open a ticket in order to discuss it with the community.
   
   
   **Expected behavior**
   
   A clear and concise description of what you expected to happen.
   
   **Environment Description**
   
   * Hudi version : 1.14.1
   
   * Flink version : 1.17.2
   
   * Hive version : 3.1.3
   
   * Hadoop version :
   
   * Storage (HDFS/S3/GCS..) :
   
   * Running on Docker? (yes/no) : no 
   
   
   **Additional context**
   
   Add any other context about the problem here.
   
   **Stacktrace**
   
   ```Add the stacktrace of the error.```
   
   


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