pravin1406 opened a new issue, #8365: URL: https://github.com/apache/hudi/issues/8365
**_Tips before filing an issue_** - Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)? yes - Join the mailing list to engage in conversations and get faster support at [email protected]. - If you have triaged this as a bug, then file an [issue](https://issues.apache.org/jira/projects/HUDI/issues) directly. **Describe the problem you faced** So just wanted the confirm the nature of some features in hudi and some about file layout. 1) While giving some old keys to the MOR table in (upsert mode with precombine key set) it creates .log files as expected, but in some cases when giving (new keys/old keys) together in a single go (upsert mode with precombine key set), it stores the updated records in a new parquet file instead of creating/updating a new .log file. So how is this behaviour controlled or is this unexpected? 2) Due to above case, i had an understanding that RO (read optimized) table will have only updated records till last compaction and any new inserts ( as they create new parquet file) made in the table visible when queried, but instead there as some updates but not all updates visible. So the RO table view gives inconsistent view as some updates will be visible some won't be. Also is there any in depth explanation/definition for RO table, is it just to read relevant parquet files simply or there is something more to it ? Thanks, please help out :/ A clear and concise description of the problem. **To Reproduce** Steps to reproduce the behavior: 1. 2. 3. 4. **Expected behavior** A clear and concise description of what you expected to happen. Hudi version : 0.12.2 Spark version : 3.2.0 Hive version : 3.1.2_1 Hadoop version : Hadoop 3.2.1 Storage (HDFS/S3/GCS..) : HDFS Running on Docker? (yes/no) : yes Add any other context about the problem here. **Stacktrace** ```Add the stacktrace of the error.``` -- 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]
