[jira] [Commented] (HIVE-21727) Allow For Ordinal Substitution
[ https://issues.apache.org/jira/browse/HIVE-21727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839621#comment-16839621 ] Greg Rahn commented on HIVE-21727: -- [~jcamachorodriguez] - Might you know? > Allow For Ordinal Substitution > --- > > Key: HIVE-21727 > URL: https://issues.apache.org/jira/browse/HIVE-21727 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Affects Versions: 4.0.0, 3.2.0 >Reporter: David Mollitor >Priority: Major > > Impala allows for ordinal substitution. Add a compatible feature to Hive to > allow Hive to be more compatible with Impala. Allows for more of a drop-in > replacement. > [IMPALA-8548] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21272) information_schema.tables should also contain views
[
https://issues.apache.org/jira/browse/HIVE-21272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Rahn updated HIVE-21272:
-
Description:
Currently it appears that INFORMATION_SCHEMA.TABLES does not contain views.
Per the ISO SQL standard,
{quote}
The INFORMATION_SCHEMA.TABLES table contains one row for each table
{color:red}including views.{color}
{quote}
Example from Postgres:
{noformat}
create table t (i int);
create view v as select i from t;
select
table_catalog,
table_schema,
table_name,
table_type
from information_schema.tables
where table_name in ('t','v');
table_catalog | table_schema | table_name | table_type
---+--++
grahn | public | t | BASE TABLE
grahn | public | v | VIEW
{noformat}
was:
Currently it appears that INFORMATION_SCHEMA.TABLES does not contain views.
Per the ISO SQL standard,
{quote}
The INFORMATION_SCHEMA.TABLES table contains one row for each table
{color:red}including views.{color}
{quote}
Example from Postgres:
{noformat}
create table t (i int);
create view v as select i from t;
select
table_catalog,
table_schema,
table_name,
table_type
from information_schema.tables
where table_schema = 'public'
and table_name in ('t','v');
table_catalog | table_schema | table_name | table_type
---+--++
grahn | public | t | BASE TABLE
grahn | public | v | VIEW
{noformat}
> information_schema.tables should also contain views
> ---
>
> Key: HIVE-21272
> URL: https://issues.apache.org/jira/browse/HIVE-21272
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema
>Affects Versions: 3.1.0
>Reporter: Greg Rahn
>Priority: Critical
>
> Currently it appears that INFORMATION_SCHEMA.TABLES does not contain views.
> Per the ISO SQL standard,
> {quote}
> The INFORMATION_SCHEMA.TABLES table contains one row for each table
> {color:red}including views.{color}
> {quote}
> Example from Postgres:
> {noformat}
> create table t (i int);
> create view v as select i from t;
> select
> table_catalog,
> table_schema,
> table_name,
> table_type
> from information_schema.tables
> where table_name in ('t','v');
> table_catalog | table_schema | table_name | table_type
> ---+--++
> grahn | public | t | BASE TABLE
> grahn | public | v | VIEW
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-15653) Some ALTER TABLE commands drop table stats
[
https://issues.apache.org/jira/browse/HIVE-15653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832119#comment-15832119
]
Greg Rahn commented on HIVE-15653:
--
I would add to the comments from [~alex.behm], stating it even more strongly --
statistics should never be explicitly removed unless it absolutely is
justified, as they are very expensive to compute. For example in RDBMS
systems, TRUNCATE, although it removes all rows, never removes statistics. I
would strongly recommend such behavior.
> Some ALTER TABLE commands drop table stats
> --
>
> Key: HIVE-15653
> URL: https://issues.apache.org/jira/browse/HIVE-15653
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 1.1.0
>Reporter: Alexander Behm
>Assignee: Chaoyu Tang
>Priority: Critical
> Attachments: HIVE-15653.patch
>
>
> Some ALTER TABLE commands drop the table stats. That may make sense for some
> ALTER TABLE operations, but certainly not for others. Personally, I I think
> ALTER TABLE should only change what was requested by the user without any
> side effects that may be unclear to users. In particular, collecting stats
> can be an expensive operation so it's rather inconvenient for users if they
> get wiped accidentally.
> Repro:
> {code}
> create table t (i int);
> insert into t values(1);
> analyze table t compute statistics;
> alter table t set tblproperties('test'='test');
> hive> describe formatted t;
> OK
> # col_namedata_type comment
>
> i int
>
> # Detailed Table Information
> Database: default
> Owner:abehm
> CreateTime: Tue Jan 17 18:13:34 PST 2017
> LastAccessTime: UNKNOWN
> Protect Mode: None
> Retention:0
> Location: hdfs://localhost:20500/test-warehouse/t
> Table Type: MANAGED_TABLE
> Table Parameters:
> COLUMN_STATS_ACCURATE false
> last_modified_byabehm
> last_modified_time 1484705748
> numFiles1
> numRows -1
> rawDataSize -1
> testtest
> totalSize 2
> transient_lastDdlTime 1484705748
>
> # Storage Information
> SerDe Library:org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe
>
> InputFormat: org.apache.hadoop.mapred.TextInputFormat
> OutputFormat:
> org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat
> Compressed: No
> Num Buckets: -1
> Bucket Columns: []
> Sort Columns: []
> Storage Desc Params:
> serialization.format1
> Time taken: 0.169 seconds, Fetched: 34 row(s)
> {code}
> The same behavior can be observed with several other ALTER TABLE commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
