matrixone
matrixone copied to clipboard
[Bug]: Constraint of Composite Primary Key is stored in tae
Is there an existing issue for the same bug?
- [X] I have checked the existing issues.
Environment
- Version or commit-id (e.g. v0.1.0 or 8b23a93):
- Hardware parameters:
- OS type:
- Others:
Actual Behavior
Currently, the Composite Primary Key is not stored as a Constraint yet
Expected Behavior
No response
Steps to Reproduce
No response
Additional information
No response
I think now cpkey is implmented in the compute layer, so Xu Peng please talk with Tian Feng, give a conclusion
I think now cpkey is implmented in the compute layer, so Xu Peng please talk with Tian Feng, give a conclusion
must be stored @bbbearxyz
in the pr #6221, Primary Key Info is stored in tae by schema.SortKey and schema.Field, return the def by engine.PrimaryIndexDef
will fix later
will fix later
It's a feature issue. And it is in the scope of #5590.
No effort until now.
No progress on this issue yet.
TableDef will be refactored after the design is finalized next week. All types of constraints will be put in a unified frame accordingly.
Working on #6616. TableDef is still in desigining.
track the progress at #5590
Refactor of TableDef has begun.
Primary key constraint will be refactored by @bbbearxyz
Has passed it on to @bbbearxyz
in the next week, after i support secondary key, i will solve this issue.
I will fix when i support all the secondary key feature.
I will fix when i support all the secondary key feature.
I will fix when i support all the secondary key feature.
I will fix after the new year rest day
i will fix it in the later
i will fix it in the later
It is being processed
This function has been completed and pr has been submitted. Please accept and test. @nnsgmsone @domingozhang @daviszhen @aunjgr @bbbearxyz
composite primary key bvt case merged ,this issue closed