-
Notifications
You must be signed in to change notification settings - Fork 3.3k
feed range query fix #46506
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
feed range query fix #46506
Changes from 8 commits
e4c4b39
fd62436
34ba12a
f99623b
f4668ab
e35c0b1
aa4b1e2
3474442
2a4538c
9a1e9df
b98cd8a
4a1b709
8b22307
7d22830
ff9eb03
ea50e6b
eb50d76
aebfe70
b19dbac
1007da5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,8 @@ | |
|
|
||
| #### Bugs Fixed | ||
| * Fixed bug where `CosmosClient` construction with AAD credentials would crash at startup if the semantic reranking inference endpoint environment variable was not set, even when semantic reranking was not being used. The inference service is now lazily initialized on first use. See [PR 46243](https://github.com/Azure/azure-sdk-for-python/pull/46243) | ||
| * Fixed a bug in `query_items(feed_range=...)` where pagination could return incorrect results after a partition split caused the supplied feed range to overlap multiple physical partitions. See [PR 46506](https://github.com/Azure/azure-sdk-for-python/pull/46506) | ||
| * Fixed `SELECT VALUE` aggregation classification across partitions: booleans are no longer treated as numeric aggregates, non-aggregate numeric projections are no longer merged, and `MIN`/`MAX` detection is now correct. See [PR 46506](https://github.com/Azure/azure-sdk-for-python/pull/46506) | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟡 Recommendation · Docs: Missing behavioral change in CHANGELOG
The CHANGELOG entry correctly calls out the boolean exclusion and non-aggregate numeric fix, but it omits a user-facing behavioral change: This is the right design choice (loud failure > silent data corruption), but users who previously depended on the (incorrect) sum-of-averages behavior will encounter an unexpected exception on upgrade. The CHANGELOG should call this out explicitly so users can prepare — e.g.:
|
||
|
|
||
| #### Other Changes | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.