fix: detect h3 column in arrow #3230
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix an issue that h3 column can not be detected when using arrow table.
in arrowSchemaToFields() function:
getFieldsFromData() was first used to detect H3 columns:
If there is a H3 column, it will be recorded in keplerFields. However, when go through the
table.schema.fields, the type and analyzeType are initialized asstringandAnalyzerDATA_TYPES.STRINGsince the H3 column is VARCHAR.So, there is a missing case for H3
Otherwise, the
typewill be overwritten as 'string', andanalyzeTypewill beAnalyzerDATA_TYPES.STRING