hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <>
Subject [jira] [Commented] (HIVE-3136) QTestUtil diff masking masks out most of 'DESCRIBE EXTENDED' output
Date Thu, 14 Jun 2012 07:26:42 GMT


Carl Steinbach commented on HIVE-3136:

Here's what the output of DESCRIBE EXTENDED looks like after it gets processed with QTestUtil.checkCliDriverResults:

PREHOOK: query: desc extended tbl2
POSTHOOK: query: desc extended tbl2
col	string	
p	string	
#### A masked pattern was here ####

And here's what it looked like before diff masking:

col	string	
p	string	
Detailed Table Information	Table(tableName:tbl2, dbName:default, owner:carl, createTime:1339652050,
lastAccessTime:0, retention:0, sd:StorageDescriptor(cols:[FieldSchema(name:col, type:string,
comment:null), FieldSchema(name:p, type:string, comment:null)], location:pfile:/Users/carl/Work/repos/hive-test/build/ql/test/data/warehouse/tbl2,
compressed:false, numBuckets:-1, serdeInfo:SerDeInfo(name:null, serializationLib:org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe,
parameters:{serialization.format=1}), bucketCols:[], sortCols:[], parameters:{}), partitionKeys:[FieldSchema(name:p,
type:string, comment:null)], parameters:{last_modified_by=carl, last_modified_time=1339652051,
PROTECT_MODE=NO_DROP_CASCADE, transient_lastDdlTime=1339652051}, viewOriginalText:null, viewExpandedText:null,

The problem with this is that many tests depend on DESC EXTENDED to verify the contents of
the StorageDescriptor, view properties, tableType, etc, etc, and all of that information is
currently getting masked out.
> QTestUtil diff masking masks out most of 'DESCRIBE EXTENDED' output
> -------------------------------------------------------------------
>                 Key: HIVE-3136
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Testing Infrastructure
>            Reporter: Carl Steinbach

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message