Skip to content
This repository was archived by the owner on Mar 12, 2026. It is now read-only.

fix: Cherry-pick commits removed in PR:1000#1013

Closed
MichaelLeeHZ wants to merge 3 commits into
apache:mainfrom
MichaelLeeHZ:fix-code-merge-error
Closed

fix: Cherry-pick commits removed in PR:1000#1013
MichaelLeeHZ wants to merge 3 commits into
apache:mainfrom
MichaelLeeHZ:fix-code-merge-error

Conversation

@MichaelLeeHZ

Copy link
Copy Markdown
Contributor

Rationale

In PR:#1000, some commits were removed.

Detailed Changes

  • cherry-pick these commits

Test Plan

ShiKaiWi and others added 3 commits June 21, 2023 17:05
The metadata for arrow schema is encoded into the parquet file. However,
this part is lost when building our custom metadata.

Keep the other metadata in the parquet metadata after extracting our
custom metadata.

Add unit test `test_arrow_meta_data` for it.
Part of apache#990.

Some background jobs are still allowed to execute, and it will lead to
data corrupted when a table is migrated between different nodes because
of multiple writers for the same table.

Introduce a flag called `invalid` in the table data to denote whether
the serial executor is valid, and this flag is protected with the
`TableOpSerialExecutor` in table data, and the `TableOpSerialExecutor`
won't be acquired if the flag is set, that is to say, any table
operation including updating manifest, altering table and so on, can't
be executed after the flag is set because these operations require the
`TableOpSerialExecutor`. Finally, the flag will be set when the table is
closed.
## Rationale
In current design, sst files may be picked multiple times.

## Detailed Changes
- Mark files as in compacting when pick files candidates, and reset it
to false when CompactionTask is dropped.

## Test Plan
Manually
@MichaelLeeHZ MichaelLeeHZ changed the title fix: Cherry-pick commits removed in pr:#1000 fix: Cherry-pick commits removed in pr-1000 Jun 21, 2023
@MichaelLeeHZ MichaelLeeHZ changed the title fix: Cherry-pick commits removed in pr-1000 fix: Cherry-pick commits removed in PR:1000 Jun 21, 2023
@ShiKaiWi

Copy link
Copy Markdown
Member

@MachaelLee I guess we should do revert on #1000, cherry-pick in this PR seems not perfect, and I'm not sure whether any other problems will be introduced.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants