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

The amount of data increased after backing up and restoring a partition-split table #1964

Open
acelyc111 opened this issue Mar 26, 2024 · 1 comment
Labels
type/bug This issue reports a bug.

Comments

@acelyc111
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
  • create a table A
  • write some data to the table A
  • count the total data on table A as number_a1
  • execute a partition-split on the table A as number_a2
  • count the total data on table A
  • back up the table A to HDFS
  • restore the data to a new table B from the backed up data from HDFS
  • count the total data on table B as number_b
  1. What did you expect to see?
    number_a1 == number_a2 == number_b

  2. What did you see instead?
    number_a1 == number_a2 != number_b

  3. What version of Pegasus are you using?
    2.4

@acelyc111 acelyc111 added the type/bug This issue reports a bug. label Mar 26, 2024
@acelyc111
Copy link
Member Author

It's because the replica.split.validate_partition_hash environment is lost on table B.

@acelyc111 acelyc111 changed the title The amount of data increased after backing up and restoring a partition-splitted table The amount of data increased after backing up and restoring a partition-split table Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug This issue reports a bug.
Projects
None yet
Development

No branches or pull requests

1 participant