CTTY opened a new issue, #10566: URL: https://github.com/apache/hudi/issues/10566
**_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 dev-subscr...@hudi.apache.org. - 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** When using `hudi-cli-with-bundle.sh` to start Hudi CLI, many commands would fail immediately due to error below: ``` 24/01/26 00:22:51 INFO InputStreamConsumer: Error: Failed to load org.apache.hudi.cli.commands.SparkMain: org/apache/hudi/common/engine/HoodieEngineContext 24/01/26 00:22:51 INFO InputStreamConsumer: 24/01/26 00:22:51 INFO ShutdownHookManager: Shutdown hook called 24/01/26 00:22:51 INFO InputStreamConsumer: 24/01/26 00:22:51 INFO ShutdownHookManager: Deleting directory /mnt/tmp/spark-5465e2a8-7b9a-4cf1-b46a-afec9f50d860 Failed to clean hoodie dataset ``` **To Reproduce** Steps to reproduce the behavior: 1. Create a Hudi table 2. Configure Spark/Hadoop/Hudi classpath for CLI and start CLI with `hudi-cli-with-bundle.sh` 3. Connect to Hudi table with command `connect --path <table_path>` 4. Run `cleans run` **Expected behavior** I believe there is 2 problems here: - CLI bundle should be working - When CLI fails, the stacktrace/error message shouldn't be truncated for debugging purposes **Environment Description** * Hudi version : 0.14.1 (I've tested with both EMR and OSS Hudi 0.14.1) * Spark version : 3.5.0 * Hive version : 3.1.3 * Hadoop version : 3.3.6 * Storage (HDFS/S3/GCS..) : S3 * Running on Docker? (yes/no) : no **Additional context** Add any other context about the problem here. **Stacktrace** See above -- 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: commits-unsubscr...@hudi.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
