Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FixIncrementalSchema #8

Closed
wants to merge 218 commits into from
Closed

FixIncrementalSchema #8

wants to merge 218 commits into from

Conversation

vinishjail97
Copy link

Tips

What is the purpose of the pull request

(For example: This pull request adds quick-start document.)

Brief change log

(for example:)

  • Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request

(Please pick either of the following options)

This pull request is a trivial rework / code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for end-to-end.
  • Added HoodieClientWriteTest to verify the change.
  • Manually verified the change by running a job locally.

Committer checklist

  • Has a corresponding JIRA in PR title & commit

  • Commit message is descriptive of the change

  • CI is green

  • Necessary doc changes done or have another open PR

  • For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

manojpec and others added 30 commits November 12, 2021 08:18
…ithmeticException (apache#3955)

- ExternalSpillableMap does the payload/value size estimation on the first put to
  determine when to spill over to disk map. The payload size re-estimation also
  happens after a minimum threshold of puts. This size re-estimation goes my the
  current in-memory map size for calculating average payload size and does attempts
  divide by zero operation when the map is size is empty. Avoiding the
  ArithmeticException during the payload size re-estimate by checking the map size
  upfront.
…nReadRollbackActionExecutor (apache#3978)

- With rollback after first commit support added to metadata table, these test cases are safe to have metadata table turned on.
Co-authored-by: 闫杜峰 <yandufeng@sinochem.com>
Co-authored-by: yuezhang <yuezhang@freewheel.tv>
…res Maven >=3.3.1 to work properly); (apache#4009)

Updated README
…strategy (apache#3950)

* Enabling timeline server based markers

* Enabling timeline server based markers and marker based rollback

* Removing constraint that timeline server can be enabled only for hdfs

* Fixing tests
- Co-authored-by: Wenning Ding <wenningd@amazon.com>
- Co-authored-by: Sivabalan Narayanan <n.siva.b@gmail.com>
Co-authored-by: Wenning Ding <wenningd@amazon.com>
- Metadata table today has virtual keys disabled, thereby populating the metafields
  for each record written out and increasing the overall storage space used. Hereby
  adding virtual keys support for metadata table so that metafields are disabled
  for metadata table records.

- Adding a custom KeyGenerator for Metadata table so as to not rely on the
  default Base/SimpleKeyGenerators which currently look for record key
  and partition field set in the table config.

- AbstractHoodieLogRecordReader's version of processing next data block and
  createHoodieRecord() will be a generic version and making the derived class
  HoodieMetadataMergedLogRecordReader take care of the special creation of
  records from explictly passed in partition names.
danny0405 and others added 28 commits December 17, 2021 13:57
…ice (apache#4347)

Co-authored-by: yuzhaojing <yuzhaojing@bytedance.com>
…en using bulkinsert to insert data which contains decimalType (apache#4253)
…th async table operations (apache#4259)

 - Adding Local JVM process based lock provider implementation

 - This local lock provider can be used by a single writer process with async
   table operations to guard the metadata tabl against concurrent updates.
…end transactions (apache#4363)

* [HUDI-3029] Transaction manager: avoid deadlock when doing begin and end transactions

 - Transaction manager has begin and end transactions as synchronized methods.
   Based on the lock provider implementaion, this can lead to deadlock
   situation when the underlying lock() calls are blocking or with a long timeout.

 - Fixing transaction manager begin and end transactions to not get to deadlock
   and to not assume anything on the lock provider implementation.
…ix and TestHoodieClientMultiWriter test fixes (apache#4384)

 - Made FileSystemBasedLockProviderTestClass thread safe and fixed the
   tryLock retry logic.

 - Made TestHoodieClientMultiWriter. testHoodieClientBasicMultiWriter
   deterministic in verifying the HoodieWriteConflictException.

Co-authored-by: yuezhang <yuezhang@freewheel.tv>
Co-authored-by: yuzhaojing <yuzhaojing@bytedance.com>
[HUDI-3008] Fixing HoodieFileIndex partition column parsing for nested fields
…with empty checkpoint (apache#4334)

* Adding ability to read entire data with HoodieIncrSource with empty checkpoint

* Addressing comments
@vinishjail97
Copy link
Author

Created by mistake. Closing the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet