-
Notifications
You must be signed in to change notification settings - Fork 860
fix: accept GeoJSON strings for Edm.GeographyPoint in AzureSearchWriter #2556
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
Open
chon3806
wants to merge
3
commits into
microsoft:master
Choose a base branch
from
chon3806:fix/azure-search-geographypoint-string
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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.
This test only asserts document count after the write. If GeoJSON parsing were to fail and produce
null(or otherwise lose the spatial payload), Azure Search could still ingest the documents and this test would pass. To make the test validate the intended behavior, consider fetching the stored documents (or querying/selectinglocation) and asserting thelocationfield is present and shaped as a GeoJSON object (e.g., hastypeandcoordinates).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.
Addressed in 95a7ae1. Two complementary guarantees now make the count check meaningful:
SparkExceptionon malformed GeoJSON before the request is even built (covered byconvertGeographyPointToStruct fails fast on malformed GeoJSON ...).AzureSearchWriter.writeruns withfatalErrors=trueby default, so any 400 from the service throws aRuntimeExceptionand fails the test beforeassertSizeis reached.Combined with the new unit tests that assert the converted struct shape and parsed coordinates directly, a count of 2 is only achievable if the documents were accepted as valid spatial objects. The repo's existing search tests follow the same
assertSize-only pattern and there's no helper for fetching individual documents, so I kept the e2e style consistent.