[
https://issues.apache.org/jira/browse/HUDI-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinoth Chandar updated HUDI-8229:
---------------------------------
Description:
In theory, given MT is another table, the reading/writing should be covered at
the table level. But - the main thing that complicates this is the use of
completion time file slicing in 1.x code to write/read MT. The problematic
combination here is 1.0/tv=6 writer and being able to continue reading the MT
from 0.14/0.15 reader.. The 1.0/tv=6 reader may handle this better since we
have control over the reader code..
Without this, we need to bring back older restrictions around MT
compaction/archival that existed in 0.x code.
was:
In theory, given MT is another table, the reading/writing should be covered at
the table level. But - the main thing that complicates this is the use of NBCC
and completion time file slicing in 1.x code to write/read MT.
Without this, we need to bring back older restrictions around MT
compaction/archival that existed in 0.x code.
> Making MT reads/writes table version specific
> ----------------------------------------------
>
> Key: HUDI-8229
> URL: https://issues.apache.org/jira/browse/HUDI-8229
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Vinoth Chandar
> Assignee: Vinoth Chandar
> Priority: Major
> Fix For: 1.0.1
>
>
> In theory, given MT is another table, the reading/writing should be covered
> at the table level. But - the main thing that complicates this is the use of
> completion time file slicing in 1.x code to write/read MT. The problematic
> combination here is 1.0/tv=6 writer and being able to continue reading the MT
> from 0.14/0.15 reader.. The 1.0/tv=6 reader may handle this better since we
> have control over the reader code..
> Without this, we need to bring back older restrictions around MT
> compaction/archival that existed in 0.x code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
