rdblue commented on a change in pull request #1902:
URL: https://github.com/apache/iceberg/pull/1902#discussion_r540509028
##########
File path: site/docs/hive.md
##########
@@ -57,7 +57,7 @@ Iceberg tables created using `HiveCatalog` are automatically
registered with Hiv
The first step is to create an Iceberg table using the Spark/Java/Python API
and `HiveCatalog`. For the purposes of this documentation we will assume that
the table is called `table_b` and that the table location is
`s3://some_path/table_b`. In order for Iceberg to correctly set up the Hive
table for querying some configuration values need to be set, the two options
for this are described below - you can use either or the other depending on
your use case.
##### Hive Configuration
-The value `iceberg.engine.hive.enabled` needs to be set to `true` and added to
the Hive configuration file on the classpath of the application creating the
table. This can be done by modifying the relevant `hive-site.xml`.
Alternatively this can be done programmatically like so:
+The value `iceberg.engine.hive.enabled` needs to be set to `true` and added to
the Hive configuration file on the classpath of the application creating or
modifying (altering, inserting etc.) the table. This can be done by modifying
the relevant `hive-site.xml`. Alternatively this can be done programmatically
like so:
Review comment:
Should we set the table property when a table is created from Hive with
this enabled? That way it would take effect for all engines by default.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
