Skip to content
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

Geometry Client V3 changes #1097

Merged
merged 4 commits into from
Dec 13, 2019
Merged

Geometry Client V3 changes #1097

merged 4 commits into from
Dec 13, 2019

Conversation

LalithaMV
Copy link
Contributor

Pull Request Template

Description

Enabling support for spatial geometry in client

• Enabling support for creating geometry collections, and adding indexes for the same in V3. Same changes for V2 is checked in: http://codeflow/extensions/launcher.html?server=https:%2f%2fmsdata.visualstudio.com%2f&projectId=ba574a88-a171-48e0-8fcb-5fef6d23739c&reviewId=357789&projectshortname=msdata

• Geometry collection content will look like:
{
"id":"Coll1",
"indexingPolicy":{
"spatialIndexes":[
{
"path":"...",
"types":[
"Point"
],
"boundingBox":
{
"xmin":xmin,
"ymin":ymin,
"xmax":xmax,
"ymax":ymax
}
}
]
},
"geospatialConfig": {"type": "Geometry"}
}

• Added tests for creating geometry spatial index in indexingPolicy test suite

Type of change

  • New feature (non-breaking change which adds functionality)

Assignee

Please add yourself as the assignee

Projects

Please add relevant projects so this issue can be properly tracked.

sboshra
sboshra previously approved these changes Dec 12, 2019
Copy link
Contributor

@sboshra sboshra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

//------------------------------------------------------------
// Copyright (c) Microsoft Corporation. All rights reserved.
//------------------------------------------------------------
namespace Microsoft.Azure.Cosmos
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should all these files be in?

namespace Microsoft.Azure.Cosmos.Spatial

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, those files are serialization related files. those had a separate folder even in V2( SharedFiles\Spatial). However this PR changes the container properties(i.e. collection content), so should remain in this namespace. Its the same even in V2, these files are directly under sharedFiles.

@sboshra sboshra merged commit e9af710 into master Dec 13, 2019
@sboshra sboshra deleted the users/laviswa/geometryClient branch December 13, 2019 01:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants