nsivabalan commented on issue #2586:
URL: https://github.com/apache/hudi/issues/2586#issuecomment-812712095
Closing this for now. please feel free to reopen or open a new ticket.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
nsivabalan commented on issue #2586:
URL: https://github.com/apache/hudi/issues/2586#issuecomment-810428893
once you respond and have any questions/clarifications, can you please
remove "awaiting-user-response" label for the issue. If possible add
"awaiting-community-help" label.
--
Th
nsivabalan commented on issue #2586:
URL: https://github.com/apache/hudi/issues/2586#issuecomment-785510794
Few options/questions:
- does your incremental ingestion contains updates or inserts? If they are
just inserts but Hudi's file sizing optimization joins w/ existing files, we
can
nsivabalan commented on issue #2586:
URL: https://github.com/apache/hudi/issues/2586#issuecomment-785128911
@bvaradar @n3nash : let me take a stab. let me know if my understanding is
right.
customers sets file versions retained to 1.
So, if there are two writes by the time a single
nsivabalan commented on issue #2586:
URL: https://github.com/apache/hudi/issues/2586#issuecomment-782850685
Hudi follows MVCC and hence there is isolation between writers and readers.
You should not see any such issues.
- "if any process updates the table under S3:. by this you mean, if
