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

TransactionDB->CreateColumnFamilyWithImport doesn't create valid column family handles #12493

Open
LIBA-S opened this issue Apr 2, 2024 · 1 comment

Comments

@LIBA-S
Copy link
Contributor

LIBA-S commented Apr 2, 2024

Note: Please use Issues only for bug reports. For questions, discussions, feature requests, etc. post to dev group: https://groups.google.com/forum/#!forum/rocksdb or https://www.facebook.com/groups/rocksdb.dev

Rocksdb Version 9.2.0

Expected behavior

After creating a Column Family through TransactionDB->CreateColumnFamilyWithImport, subsequent transaction writes should be processed correctly.

Actual behavior

Error occurred while writing data: Column family id not found.

Steps to reproduce the behavior

  1. Open a column family with TransactionDB->CreateColumnFamilyWithImport
  2. Begin a transaction and write data to the column family

The specific reason for the error is similar to this issue: #10322

@LIBA-S
Copy link
Contributor Author

LIBA-S commented Apr 2, 2024

Regarding this issue, I have submitted a fix PR #12490

facebook-github-bot pushed a commit that referenced this issue Apr 3, 2024
Summary:
When we use the CreateColumnFamilyWithImport interface of PessimisticTransactionDB to create column family, the lack of related information may cause subsequent writes to be unable to find the Column Family ID.

The issue: (#12493)

Pull Request resolved: #12490

Reviewed By: jowlyzhang

Differential Revision: D55700343

Pulled By: cbi42

fbshipit-source-id: dc992a3eef433e1193d579cbf58b6ba940fa460d
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

No branches or pull requests

1 participant