metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From LosD <>
Subject [GitHub] metamodel issue #133: Don't get killed by Hive SQLExceptions when finding de...
Date Tue, 11 Oct 2016 14:52:11 GMT
Github user LosD commented on the issue:
    Okay, that should fix it.
    BTW, another curious thing with Hive on JDBC: Hive inserts are _very_ slow, since it's
starting a MapReduce job for every insert... So you'd expect them to prioritize the batch
feature? Nope. No support. Every... Single... Insert... Becomes... It's... Own... Job... I
think the integration test job uses around 10-15 seconds per insert on my laptop (granted,
with Hive running in the MapR sandbox on VirtualBox, but the VM overhead shouldn't really
be noticable).
    I have a feeling that JDBC isn't really prioritized, so we might at some point see if
there's another more low-level API to connect to Hive.
    On the other hand, querying is fast, so in that regard it's fine.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message