-
Notifications
You must be signed in to change notification settings - Fork 11
fix(csharp): normalize TypeName once in TryGetSchemaFromManifest #337
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
47ba26e
fix(csharp): normalize TypeName once in TryGetSchemaFromManifest; add…
eric-wang-1990 cc71688
test(csharp): remove redundant Spark:DataType:SqlName assertion from …
eric-wang-1990 4254d7c
test(csharp): remove ComplexAndDecimalTypesAreMappedCorrectly test
eric-wang-1990 3860e05
test(csharp): move null TypeName coverage to ColumnMetadataHelperTests
eric-wang-1990 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Why need add these, we already have csharp/test/ColumnMetadataHelperTests.cs which test all type mapping?
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.
Good point — removed the redundant
Spark:DataType:SqlNameassertion for DECIMAL (already covered byColumnMetadataHelperTests).Kept the two tests because they cover things
ColumnMetadataHelperTestsdoesn't:ComplexAndDecimalTypesAreMappedCorrectly: exercisesMapDatabricksTypeToArrowTypeend-to-end (e.g.DECIMAL(10,2)→Decimal128Type,ARRAY→StringType) — the existingArrowTypesAreMappedCorrectlytest doesn't include these typesNullTypeName_TreatedAsUnknownType: verifies nullTypeNamedoesn't throw — not covered anywhere elseThere 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.
You're right, removed it. The production change is just extracting a
typeNamelocal — the complex/decimal type mapping is out of scope.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.
Moved it — added
[InlineData("", "")]to the existingGetBaseTypeNameandGetSparkSqlNametheories inColumnMetadataHelperTestsand removed the statement-level test entirely.