• Documentation
    • Search documentation
    karat

    +

    K

    API Reference ↗
    Data connectivity & integrationAvailable connectorsApache Hive

    Apache Hive

    The Apache Hive connector is a Palantir-provided driver for Apache Hive.

    To create a new Apache Hive source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Apache Hive-specific configuration and networking. For the complete property reference, see the official Apache Hive driver documentation ↗.

    Beta

    The Apache Hive connector is in the beta phase of development and may not be available on your enrollment. Functionality may change during active development.

    Supported capabilities

    CapabilityStatus
    Exploration🟡 Beta
    Batch syncs🟡 Beta
    Incremental🟡 Beta
    Table exports🟡 Beta

    Configuration

    The properties below are mandatory or recommended.

    PropertyRequired?DescriptionDefault
    AuthScheme ↗MandatoryThe authentication scheme used. Accepted entries are Anonymous, Plain, LDAP, NoSasl, and Kerberos.Anonymous
    Server ↗MandatoryThe host name or IP address of the server hosting HiveServer2.{serverAddress}
    UseSSL ↗MandatorySpecifies whether to use SSL Encryption when connecting to Hive.TRUE
    Database ↗RecommendedThe name of the Hive database to use by default.—
    Password ↗RecommendedThe password used to authenticate with Hive.—
    Port ↗RecommendedThe port for the connection to the HiveServer2 instance.10000
    SSLServerCert ↗RecommendedSpecifies the certificate to be accepted from the server when connecting using TLS/SSL.—
    TransportMode ↗RecommendedThe transport mode to use to communicate with the Hive server. Accepted entries are BINARY and HTTP.BINARY
    User ↗RecommendedThe username used to authenticate with Hive.—

    Networking

    The table below lists the domains that the source must be able to access to run.

    For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead. The agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.

    DomainRequired
    <Server>:<Port>Always
    <KerberosKDC>:88If AuthScheme=Negotiate
    <KerberosServiceKDC>:88If AuthScheme=Negotiate and Kerberos topology uses multiple realms

    Table exports

    This connector supports table exports. Learn how to set up a table export.