[
https://issues.apache.org/jira/browse/IMPALA-9264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
WangSheng updated IMPALA-9264:
------------------------------
Description:
In my company, catalogd connected to mysql/pg directly (instead of by metastore
service) is a very common usage. And we just need to config hive-site.xml like
this(metastore related config such as hive.metastore.uris is unnecessary):
{code:java}
<property>
<name>javax.jdo.option.ConnectionDriverName</name>
<value>org.postgresql.Driver</value>
</property>
<property>
<name>javax.jdo.option.ConnectionPassword</name>
<value>password</value>
</property>
<property>
<name>javax.jdo.option.ConnectionURL</name>
<value>jdbc:postgresql://localhost:5432/HMS_home_impala</value>
</property>
<property>
<name>javax.jdo.option.ConnectionUserName</name>
<value>hiveuser</value>
</property>
{code}
Recently, when I test impala-3.3 in this situation, I found that created kudu
managed table failed
([IMPALA-8974|https://issues.apache.org/jira/browse/IMPALA-8974]), and I've
already fixed this.
I guess there maybe other funcionality that have not been took into
considertion in this situation. So I built this jira to collect those
functionality, and I'm willing to continue contributing when I'm free.
was:
In my company, catalogd connected to mysql/pg directly (instead of by metastore
service) is a very common usage. And we just need to config hive-site.xml like
this(metastore related config such as hive.metastore.uris is unnecessary):
{code:java}
<property>
<name>javax.jdo.option.ConnectionDriverName</name>
<value>org.postgresql.Driver</value>
</property>
<property>
<name>javax.jdo.option.ConnectionPassword</name>
<value>password</value>
</property>
<property>
<name>javax.jdo.option.ConnectionURL</name>
<value>jdbc:postgresql://localhost:5432/HMS_home_impala</value>
</property>
<property>
<name>javax.jdo.option.ConnectionUserName</name>
<value>hiveuser</value>
</property>
{code}
Recently, when I test impala-3.3 in this situation, I found that created kudu
managed table failed
([IMPALA-8974|https://issues.apache.org/jira/browse/IMPALA-8974]), and I've
already fixed this.
I guess there maybe other functions that have not been took into considertion
in this situation. So I built this jira to collect those functions, and I'm
willing to continue contributing when I'm free.
> Support catalogd without HMS
> ----------------------------
>
> Key: IMPALA-9264
> URL: https://issues.apache.org/jira/browse/IMPALA-9264
> Project: IMPALA
> Issue Type: Improvement
> Affects Versions: Impala 3.3.0
> Reporter: WangSheng
> Assignee: WangSheng
> Priority: Major
>
> In my company, catalogd connected to mysql/pg directly (instead of by
> metastore service) is a very common usage. And we just need to config
> hive-site.xml like this(metastore related config such as hive.metastore.uris
> is unnecessary):
> {code:java}
> <property>
> <name>javax.jdo.option.ConnectionDriverName</name>
> <value>org.postgresql.Driver</value>
> </property>
> <property>
> <name>javax.jdo.option.ConnectionPassword</name>
> <value>password</value>
> </property>
> <property>
> <name>javax.jdo.option.ConnectionURL</name>
> <value>jdbc:postgresql://localhost:5432/HMS_home_impala</value>
> </property>
> <property>
> <name>javax.jdo.option.ConnectionUserName</name>
> <value>hiveuser</value>
> </property>
> {code}
> Recently, when I test impala-3.3 in this situation, I found that created kudu
> managed table failed
> ([IMPALA-8974|https://issues.apache.org/jira/browse/IMPALA-8974]), and I've
> already fixed this.
> I guess there maybe other funcionality that have not been took into
> considertion in this situation. So I built this jira to collect those
> functionality, and I'm willing to continue contributing when I'm free.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
