[ 
https://issues.apache.org/jira/browse/HIVE-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146240#comment-14146240
 ] 

Damien Carol commented on HIVE-7689:
------------------------------------

[~alangates] I understand more clearly now why you have some concerns regarding 
that JIRA.
bq. Are you concerned that having upper case names for DataNucleus generated 
tables but lower case names for transaction tables is confusing? I don't see 
that as an issue since these tables are not a public interface.
First time I launched the script for posgres, I saw the new tables was lower 
case but all other tables was in upper case. I believed it was a bug. If this 
not an issue, I think we can close this JIRA.

It's just confusing. Every tables in Metastore rely on same upper case policy 
and naming conventions.

The only problem is when we will extend Jdbc stats provider or provide access 
to this lower cased tables though DataNucleus.
Plus if we want to support a new Database for back-end that don't rely on 
"default lower case" behavior.

> Enable Postgres as METASTORE back-end
> -------------------------------------
>
>                 Key: HIVE-7689
>                 URL: https://issues.apache.org/jira/browse/HIVE-7689
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 0.14.0
>            Reporter: Damien Carol
>            Assignee: Damien Carol
>            Priority: Minor
>              Labels: metastore, postgres
>             Fix For: 0.14.0
>
>         Attachments: HIVE-7689.5.patch, HIVE-7689.6.patch, HIVE-7689.7.patch, 
> HIVE-7689.8.patch, HIVE-7889.1.patch, HIVE-7889.2.patch, HIVE-7889.3.patch, 
> HIVE-7889.4.patch
>
>
> I maintain few patches to make Metastore works with Postgres back end in our 
> production environment.
> The main goal of this JIRA is to push upstream these patches.
> This patch enable LOCKS, COMPACTION and fix error in STATS on postgres 
> metastore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to