[
https://issues.apache.org/jira/browse/HIVE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229977#comment-15229977
]
Qiuzhuang Lian commented on HIVE-11981:
---------------------------------------
nope, our table doesn't have any struct. here is the DDL,
CREATE TABLE `my_orc_table`(
`id` string,
`store_no_from` string,
`store_name_from` string,
`store_no_to` string,
`store_name_to` string,
`order_unit_no_from` string,
`order_unit_name_from` string,
`order_unit_no_to` string,
`order_unit_name_to` string,
`store_no` string,
`store_name` string,
`company_no` string,
`order_unit_no` string,
`order_unit_name` string,
`item_no` string,
`item_code` string,
`item_name` string,
`brand_no` string,
`brand_name` string,
`category_no` string,
`sku_no` string,
`size_no` string,
`size_kind` string,
`bill_no` string,
`status` tinyint,
`bill_type` int,
`in_out_flag` tinyint,
`ref_bill_no` string,
`ref_bill_type` int,
`biz_type` int,
`account_type` tinyint,
`bill_date` date,
`cost` decimal(12,2),
`balance_offset` int,
`balance_qty` int,
`factory_in_offset` int,
`factory_in_qty` int,
`factory_in_diff_offset` int,
`factory_in_diff_qty` int,
`transit_in_offset` int,
`transit_in_qty` int,
`transit_out_offset` int,
`transit_out_qty` int,
`in_diff_offset` int,
`in_diff_qty` int,
`out_diff_offset` int,
`out_diff_qty` int,
`transit_in_account_offset` int,
`transit_in_account_qty` int,
`transit_out_account_offset` int,
`transit_out_account_qty` int,
`in_diff_account_offset` int,
`in_diff_account_qty` int,
`out_diff_account_offset` int,
`out_diff_account_qty` int,
`lock_offset` int,
`lock_qty` int,
`occupied_offset` int,
`occupied_qty` int,
`backup_offset` int,
`backup_qty` int,
`guest_bad_offset` int,
`guest_bad_qty` int,
`original_bad_offset` int,
`original_bad_qty` int,
`bad_transit_offset` int,
`bad_transit_qty` int,
`bad_diff_offset` int,
`bad_diff_qty` int,
`return_offset` int,
`return_qty` int,
`borrow_offset` int,
`borrow_qty` int,
`create_time` timestamp,
`create_timestamp` timestamp,
`update_time` timestamp,
`sharding_flag` string,
`yw_update_time` timestamp,
`hive_create_time` timestamp,
`biz_date` int)
CLUSTERED BY (
id)
INTO 10 BUCKETS
ROW FORMAT SERDE
'org.apache.hadoop.hive.ql.io.orc.OrcSerde'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.orc.OrcInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat'
LOCATION
'hdfs://nn:9000/hive/warehouse/lqz.db/my_orc_table'
TBLPROPERTIES (
'COLUMN_STATS_ACCURATE'='{\"BASIC_STATS\":\"true\"}',
'last_modified_by'='hive',
'last_modified_time'='1460015324',
'numFiles'='23',
'numRows'='33828471',
'orc.compress'='SNAPPY',
'orc.create.index'='true',
'orc.stripe.size'='67108864',
'rawDataSize'='92332902940',
'totalSize'='1474582939',
'transactional'='true',
'transient_lastDdlTime'='1460015745')
> ORC Schema Evolution Issues (Vectorized, ACID, and Non-Vectorized)
> ------------------------------------------------------------------
>
> Key: HIVE-11981
> URL: https://issues.apache.org/jira/browse/HIVE-11981
> Project: Hive
> Issue Type: Bug
> Components: Hive, Transactions
> Reporter: Matt McCline
> Assignee: Matt McCline
> Priority: Critical
> Labels: TODOC2.0
> Fix For: 2.0.0
>
> Attachments: HIVE-11981.01.patch, HIVE-11981.02.patch,
> HIVE-11981.03.patch, HIVE-11981.05.patch, HIVE-11981.06.patch,
> HIVE-11981.07.patch, HIVE-11981.08.patch, HIVE-11981.09.patch,
> HIVE-11981.091.patch, HIVE-11981.092.patch, HIVE-11981.093.patch,
> HIVE-11981.094.patch, HIVE-11981.095.patch, HIVE-11981.096.patch,
> HIVE-11981.097.patch, HIVE-11981.098.patch, HIVE-11981.099.patch,
> HIVE-11981.0991.patch, HIVE-11981.0992.patch, ORC Schema Evolution Issues.docx
>
>
> High priority issues with schema evolution for the ORC file format.
> Schema evolution here is limited to adding new columns and a few cases of
> column type-widening (e.g. int to bigint).
> Renaming columns, deleting column, moving columns and other schema evolution
> were not pursued due to lack of importance and lack of time. Also, it
> appears a much more sophisticated metadata would be needed to support them.
> The biggest issues for users have been adding new columns for ACID table
> (HIVE-11421 Support Schema evolution for ACID tables) and vectorization
> (HIVE-10598 Vectorization borks when column is added to table).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
