architlatkar27 opened a new issue, #19963:
URL: https://github.com/apache/hudi/issues/19963
### Describe the problem you faced
We are using gravitino as a catalog manager on top of a Hudi fileset. In
spark when we try to read a file like `gvfs://path/to/file.hudi` we get the
below error
`Caused by: java.lang.IllegalArgumentException: Unsupported scheme :gvfs
at
org.apache.hudi.storage.StorageSchemes.isWriteTransactional(StorageSchemes.java:144)`
### To Reproduce
1. In gravitino register a file catalog with the catalog having hudi files
2. Create a spark job to read/write files from the above catalog and run it
### Expected behavior
We should be able to read/write hudi files through gravitino's gvfs
filesystem.
### Environment Description
* Hudi version: 1.2.0
* Spark version: 3.5, 4.1 etc.
* Flink version: NA
* Hive version: NA
* Hadoop version: NA
* Storage (HDFS/S3/GCS..): Gravitino based gvfs - it can s3, hdfs, gcs etc.
internally
* Running on Docker? (yes/no): No
### Additional context
In gravitino the filesystem is abstracted as gvfs://path/to/file... Here
the underlying filesystem could be any filesystem like hdfs, gcs etc.
We get Unsupported Exception in spark while reading the hudi file since hudi
is not able to recognize `gvfs` as a storage scheme like hdfs, gcs etc.
### Stacktrace
```shell
Caused by: java.lang.IllegalArgumentException: Unsupported scheme :gvfs
at
org.apache.hudi.storage.StorageSchemes.isWriteTransactional(StorageSchemes.java:144)
at
org.apache.hudi.common.table.log.HoodieLogFileReader.isBlockCorrupted(HoodieLogFileReader.java:262)
at
org.apache.hudi.common.table.log.HoodieLogFileReader.readBlock(HoodieLogFileReader.java:143)
at
org.apache.hudi.common.table.log.HoodieLogFileReader.next(HoodieLogFileReader.java:383)
at
org.apache.hudi.common.table.log.HoodieLogFormatReader.next(HoodieLogFormatReader.java:102)
at
org.apache.hudi.common.table.log.BaseHoodieLogRecordReader.scanInternalV1(BaseHoodieLogRecordReader.java:227)
... 86 more
```
--
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]
