wombatu-kun commented on code in PR #11559: URL: https://github.com/apache/hudi/pull/11559#discussion_r1665537491
########## rfc/rfc-80/rfc-80.md: ########## @@ -0,0 +1,161 @@ +<!-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to You under the Apache License, Version 2.0 + (the "License"); you may not use this file except in compliance with + the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +# RFC-80: Support column families for wide tbles + +## Proposers + +- @xiarixiaoyao +- @wombatu-kun + +## Approvers + - + - + +## Status + +JIRA: https://issues.apache.org/jira/browse/HUDI- + +## Abstract + +In streaming processing, there are often scenarios where the table is widened. The current mainstream real-time stretching is completed through Flink's multi-layer join; +Flink's join will cache a large amount of data in the state backend. As the data set increases, the pressure on the Flink task state backend will gradually increase, and may even become unavailable. Review Comment: As this overall design relies on NB-CC support, it is necessary anyway. I don't think that it can ease a lot for the scenario when multiple writers ingest their own subset of columns while readers want to read different subsets or the whole set of columns. Both writing, reading and compacting will be complicated and not very performant. And if we separate ingestion to different tables, we'll have to join them on reading. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
