provides several metastore commands to allow your metadata (managed by the metastore) to have the same ‘versions’ as your data (managed by lakeFS). To create your first table, you would have to use the metastore’s
commands (e.g. Hive) - not a
command. I think that lakeFS flow with metastore is summed up nicely in this doc. Let me know if your use-case isn’t covered there..
. Your question depends on the application you choose to process the data. For Athena, you need symlinks. For Spark, you can simply change the
). For Athena to be able to query lakeFS data it needs to get the paths from lakeFS. That’s where the
lakectl metastore create-symlinks
command does behind the scenes.
I'm following documentation here
must specify 1-based parent number for reverting merge commit
-m, --parent-number int the parent number (starting from 1) of the mainline. The revert will reverse the change relative to the specified parent.