idrismike commented on issue #6942: URL: https://github.com/apache/hudi/issues/6942#issuecomment-1279098063
As mentioned above, writing to `azure abfss` with `hoodie.metadata.enable=false` works. But then, async indexing Fails using `HoodieIndexer`  Since both `hoodie.metadata.enable=true` and `HoodieIndexer` generate metadata - the problem seems similar. Therefore, cannot really upgrade until and unless these issues are resolved. **PS**: currently, the `HoodieIndexer` takes two parameters `--base-path` and `--table-name`. I would imagine `basepath` to be the directory that contains the `table` - but the indexer only works if `base-path` also contains the table name . e.g. Imagine storage container to be on the path `abfss://[email protected]/some/path/to/storage/container` and a table there `test_table`. Then, the `base-path` should be `abfss://[email protected]/some/path/to/storage/container` and the `table-name` should be `test_table`. But what my experience with `HoodieIndexer` is that, the `base-path` must be `abfss://[email protected]/some/path/to/storage/container/test_table` and the `tabel-name` to be `test_table`. That works but seems bit weird. -- 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]
