Clean-up and clarify Hive import documentation

[exalate-issue-sync]

No description provided.

[exalate-issue-sync]

Michal Kurka commented: Users are confused about the right way to import data to H2O using Hive: [http://docs.h2o.ai/h2o/latest-stable/h2o-docs/getting-data-into-h2o.html#direct-hive-import|http://docs.h2o.ai/h2o/latest-stable/h2o-docs/getting-data-into-h2o.html#direct-hive-import]

Some people end-up using JDBC interface which is known to be sub-optimal.

We need to make sure there is a clearly preferred method, with a clear description. We also need to make sure the documentation doesn’t list Hive support as experimental.

Feedback from [~accountid:5d1185d20d64020c403ab5de]

{quote}Our documentation says "This feature is still experimental. In addition, Hive2 support in H2O is not yet suitable for large datasets."

{quote}

[exalate-issue-sync]

Michal Kurka commented: Also not just for Hive, but JDBC in general:

The handling of categorical values is different between file ingest and JDBC ingests: the JDBC treats categorical-values as Strings. Strings are not compressed in any way in H2O memory and using JDBC interface might need more memory and additional data post-processing (converting to categoricals explicitly).

[exalate-issue-sync]

Angela Bartz commented: Pull request #4528 submitted to rel-zahradnik.

[exalate-issue-sync]

Angela Bartz commented: Pull request #4528 merged into rel-zahradnik.

[h2o-ops]

JIRA Issue Migration Info

Jira Issue: PUBDEV-7343
Assignee: Angela Bartz
Reporter: Michal Kurka
State: Resolved
Fix Version: 3.30.0.3
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#4528