You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, the GraphAr C++ and Spark libraries supports only several basic data types (including BOOL, INT32, INT64, FLOAT, DOUBLE, and STRING). To serve more scenarios, more built-in data types need to be added in GraphAr libraries.
Describe the solution you'd like
Add more common data types to the GraphAr libraries, such as DATE, TIME, BINARY, STRUCT, MAP, ARRARY, and JSON. Since these types are not always supported by the CSV/ORC/Parquet file types and the C++/Spark standard libraries, careful handling should be taken in each case, e.g., performing the necessary type conversions.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
lixueclaire
changed the title
[Feat] Extend the built-in data types of GraphAr libraries
[Feat] Include additional built-in data types for GraphAr libraries
Jan 12, 2023
Is your feature request related to a problem? Please describe.
Currently, the GraphAr C++ and Spark libraries supports only several basic data types (including BOOL, INT32, INT64, FLOAT, DOUBLE, and STRING). To serve more scenarios, more built-in data types need to be added in GraphAr libraries.
Describe the solution you'd like
Add more common data types to the GraphAr libraries, such as DATE, TIME, BINARY, STRUCT, MAP, ARRARY, and JSON. Since these types are not always supported by the CSV/ORC/Parquet file types and the C++/Spark standard libraries, careful handling should be taken in each case, e.g., performing the necessary type conversions.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: