Re: [I] Failed to read S3 multi-path for hudi datasource after 0.12.0 [hudi]

["nsivabalan (via GitHub)" <gi...@apache.org>]

nsivabalan commented on issue #16209:
URL: https://github.com/apache/hudi/issues/16209#issuecomment-4795554422

   Triage update: this is no longer reproducible on `master`. PR #14060 (commit `2ebc6775`, _refactor(spark): Remove glob paths and deprecate read paths support_) deprecated `hoodie.datasource.read.paths` and removed glob-path support for the v1 datasource. The confusing `Wrong basePath ... for the root path ...` error is replaced by an explicit, upfront rejection in `DefaultSource.scala`:
   
   ```scala
   if (path.exists(_.contains("*")) || readPaths.nonEmpty) {
     throw new HoodieException("Glob paths are not supported for read paths as of Hudi 1.2.0")
   }
   ```
   
   The specific failure mode reported here is gone, but note that the original use case (reading multiple distinct Hudi tables in a single `spark.read` via comma-separated globs) is intentionally unsupported going forward — please use a `union` of per-table reads instead. Closing as resolved by deprecation/removal; please reopen if you hit a regression on master.


-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org