-
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
Physical type #1549
Physical type #1549
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1549 +/- ##
========================================
Coverage 91.91% 91.92%
========================================
Files 693 696 +3
Lines 24809 24958 +149
========================================
+ Hits 22804 22942 +138
- Misses 2005 2016 +11
☔ View full report in Codecov by Sentry. |
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.
I have general questions about when to use physical type and how many getDataTypeSize we should maintain. Let's discuss together @acquamarin @ray6080
1. Physical datatType VS Logical dataType
Physical Data Types: Represents the actual representations of data in memory or on disk. Two difference logical dataTypes may have the same physical dataType. (E.g. The internal representation of INT32 and DATE is INT32)
Logical Data Types: Represents how the data is perceived and used in queries. Logical data types help determine what operations are valid for a piece of data and how those operations should behave.
2. Todo:
Refactor storage code to use physical dataType instead of logical dataType.