nsivabalan commented on a change in pull request #2739:
URL: https://github.com/apache/hudi/pull/2739#discussion_r615827120
##########
File path: docs/_posts/2021-02-13-hudi-key-generators.md
##########
@@ -5,18 +5,16 @@ author: shivnarayan
category: blog
---
-Every record in Hudi is uniquely identified by a HoodieKey, which is a pair of
record key and partition path where the
-record belongs to. Hudi has imposed this constraint so that updates and
deletes can be applied to the record of interest.
-Hudi relies on the partition path field to partition your dataset and records
within a partition have unique record keys.
-Since uniqueness is guaranteed only within the partition, there could be
records with same record keys across different
-partitions. One should choose the partition field wisely as it could be a
determining factor for your ingestion and
-query latency.
+Every record in Hudi is uniquely identified by a primary key, which is a pair
of record key and partition path where
+the record belongs to. Using primary keys, Hudi can impose a) partition level
uniqueness integrity constraint
Review comment:
yeah. I did have it in my initial draft. But guess nishith feedback was
to not go into too much details. let me sync up w/ him again.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
