-
Notifications
You must be signed in to change notification settings - Fork 85
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
Add SERIAL as node table primary key #1493
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1493 +/- ##
==========================================
- Coverage 92.20% 92.18% -0.03%
==========================================
Files 671 671
Lines 24069 24123 +54
==========================================
+ Hits 22194 22238 +44
- Misses 1875 1885 +10
☔ View full report in Codecov by Sentry. |
assert(structureIDAndFName.storageStructureID.columnFileID.columnType == | ||
ColumnType::REL_PROPERTY_COLUMN); | ||
StorageStructureType::COLUMN && | ||
structureIDAndFName.storageStructureID.columnFileID.columnType == |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not related to this PR but I really hate this structureIDAndFName.storageStructureID.storageStructureType
naming and call chain.
I think we should just use s
to stand for storageStructure
. It's insane to see storageStructure
everywhere as a naming prefix.
This PR introduces
SERIAL
as a special data type for primary key properties, whose values are same as internal node offsets. This can speed up data ingestion, as no index construction/lookup is required during data ingestion.SERIAL
is limited to primary key of node tables only for now.This PR hasn't handled updates, index scan, and expression evaluations over
SERIAL
. See #1496 .