Check token refresh offset after read from cache #22
Conversation
This file contains 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
SyncReceiver: Queue up the receive request and process them one at a time
* generate mr 2020 05 * update pom
* feat: update pom after generation * fix: write back to pom
* feat: add spotbugs in CI and suppress revapi error in release * feat: remove identity from mgmt * fix: resources test depends on azure identity * fix: playbackServerPort is used in code
* mgmt update default subscription logic * fix checkstyle * fix comment * use IllegalStateException instead of RuntimeException * update description
* add spring boot for key vault * include property file * address review comments * add azure-spring-boot in jacoco-test-coverage pom file to make build-from-source successful * upgrade azure-identity version used in spring-boot * move Spring versions to version_client.txt to keep consistency * add CHANGELOG.md * add configurations for JavaDoc plugins and entries in jacoco-test-coverage * fix artifact id of key-vault-starter in docs * fix artifact id of aad-starter in docs Co-authored-by: Xiaolu Dai <[email protected]>
* NetApp: regenerate package-2019-11 * update pom
* Kusto: generate package-2020-02-15 * update pom * fix compile errors
…vert windows version. (Azure#11388)
* Increment package version after release of com.microsoft.azure azure-eventhubs * Increment package version after release of com.microsoft.azure azure-eventhubs-eph * Increment package version after release of com.microsoft.azure azure-eventhubs-extensions
…and CreationTime, along with TTL header. (Azure#11354) TTL field in the message header is of type unsigned integer, so it cannot support TTL values larger than 50 days when converted to milliseconds. So reading TTL as the difference between AbsoluteExpiryTime and CreationTime properties on the AMQP message.
* - Fixes issue where VALUE order by queries fail parsing the order by elements
- Fixes the result format of SELECT VALUE queries including aggregate queries
something like {"_value": "2.6"} would now be {2.6} which corresponds to wire data.
- This also enables better support for extracting the results into non key value types like Integer, Double etc.
* Reverting an unwanted change
* Fixing issue
* Fixing failing tests
* Adding double and boolean value query tests
* Adding more tests
- to validate downcast cases
- to validate user type with _value doesnt cause any issue
* ensure doc repo is present everywhere you call archtype-java-release
Add more explanation in SessionHandlerOptions to help customers understand more about how the parameters impact throughput.
…ssued by AAD (Azure#11235) * apply pr of skiping aad internal filter * modify for checkstyle
* Update Change Feed Processor public APIs and documentation. * Add implementation and respective test case for estimating the Change Feed Processor lag between the last processed batch of feeds (check-pointed in the respective lease document) and the latest feed document. * Remove container readAllItems() from public API surface. Add new APIs for createContainerIfNotExists() that will accept a throughput properties object. Fix docs; finish sentences with ".", rewording. * Add createDatabaseIfNotExist() method that takes a throughput properties object. Doc changes: finish sentences with ".". * Remove readProvisionedThroughput() and replaceProvisionedThroughput(); with the introduction of auto-scale features the throughput must be explicitly handled via ThroughputProperties class. Fix Java doc issue; remove unsopported "@see" annotation. * Remove/refactor public APIs that take throughput as an integer to use a full throughput properties object.
* MediaServices: regenerate package-2018-07 * update pom
* update AzureProfile * update samples for profile change
* add servicebus-jms starter and metrics starter * add azure-spring-boot dependency in jacoco * upgrade spring-jms version and define spring modules verion in version_client * add CHANGELOG.md * add configurations for JavaDoc plugins and entries in jacoco-test-coverage Co-authored-by: Xiaolu Dai <[email protected]>
* migrate aad-b2c * update README.md and add b2c samples * add comments on aad b2c classes * update copyright and code comment * update for checkstyle * add azure spring boot in jacoco * add test for aad b2c * move module decleration from version_data.txt to version_client.txt * update spring-web version * add CHANGELOG.md * add entries in jacoco and plugin for javadoc Co-authored-by: Xiaolu Dai <[email protected]>
* migrate cosmosdb and gremlin * add code comment * delete lombok and unused test code * modify readme for version tag * modify readme for version tag and add example * add include lib for enforcer * modify for checkstyle * add CHANGELOG.md * add entries in jacoco and plugin for javadoc Co-authored-by: Xiaolu Dai <[email protected]>
* remove pagination feature
…1471) * autogenerated swagger files and pom.xml * adding readme file * changing README and pom file to be based on template * fixing with naming, version and things connie suggested * Fixed pom and some version issues which were in Jim's comments * pom file changes * fix swagger location and pom mistake * quick fixes * regenerated swaggger, fix build issue * readme fix
* Added SDK version to CosmosException and unit tests * Added user agent to both exception and diagnostics
…cs (Azure#11592) * Removing extra class CosmosAsyncItemResponse * deleting the file came back in merge conflict * doc correction
Co-authored-by: Annie Liang <[email protected]>
* init * remove kafka * azure- artifact ids * azure-core + version change * progress snapshot before swapping autorest client * swagger generated http client * update common package * junit engine * fix versioning * javadoc checkstyle * javadoc checkstyle * checkstyle javadoc * spotbugs override for serializing null value * add service client annotation * service client style * fix dep management tags * add module-info and initial readme * add readme sections * fix readme section case * add src clients to jacoco * add latest swagger * add basic readme intros * Update sdk/schemaregistry/azure-schemaregistry-client/src/main/java/com/azure/schemaregistry/client/CachedSchemaRegistryClient.java Co-authored-by: Alan Zimmer <[email protected]> * fix comments * Update sdk/schemaregistry/azure-schemaregistry-client/src/main/java/com/azure/schemaregistry/client/CachedSchemaRegistryClient.java Co-authored-by: Alan Zimmer <[email protected]> * default retry policy on null * remove unused headers policy * netty dep * hashmap to concurrent hashmap, slf4j format pattern * builder cleanup * remove runtime error from method signature * comments * change group name * move rest service builder * update dirs and repo files * update package structure * update versioning * fix jacoco test pom * fix eng system comments * Update sdk/schemaregistry/azure-data-schemaregistry-avro/pom.xml Co-authored-by: Alan Zimmer <[email protected]> * Update sdk/schemaregistry/azure-data-schemaregistry-avro/src/main/java/com/azure/data/schemaregistry/avro/SchemaRegistryAvroDeserializer.java Co-authored-by: Alan Zimmer <[email protected]> * fix comments * spotbugs update Co-authored-by: Alan Zimmer <[email protected]>
…zure#11646) * Removing double retries for creating receive link and other fixes * Remove unused imports * Remove empty line
* disable after-burner for rntbd debug log messages * cleanup
* Updated readme to follow general guidelines * Fixed broken links in readme * Added maven central link and java docs keyword
* SignalR: generate package-2020-05 * update pom.mgmt.xml * regenerate with autorest v2
* Hide DataType and all Index types * resolve comments Co-authored-by: Annie Liang <[email protected]>
* ProxyOptions change * resolve comments * fix Co-authored-by: Annie Liang <[email protected]>
* Create empty sources.jar with README.md contents * Update a comment
Co-authored-by: Annie Liang <[email protected]>
* Address API review feedback * Fixed the service method
…and RntbdTransportClient.Options (Azure#11595) * Port from v4 * Corrected package misspelling in log4j.properties and removed System.exit from Main.java * Responded to code review comments * Updated sdk/cosmos/README.md with info on using system properties to modify default Direct TCP options * Ported memory leak from v2.6.X and bumped version number. * Removed a file that was mistakenly committed * Space adjustments for readability * DCDocumentCrudTest passes. Performance, reliability, and scalability tuning/testing work remains. * Enabled channel acquisition timeout interval default: 100 ms Verified: direct tests pass modulo a mockito issue that breaks a number of direct tests. Root cause analysis on the mockito break is TBD. * Removed some newlines * Added a newline at the end of file * Ensured that RntbdClientChannelPool.release never throws and never releases a channel prematurely. This change addresses occassional point read failures (~0.0015% of the time in local testing) when slamming a partition with read requests. This change also ensures that unhandled exceptions during release do not cause thread deaths. * Revised channel acquisition algorithm such that no timer acquisition task timeout is used by default and we allow maxRequestsPerChannel to go above limit when maxChannels are allocated * Attempt to resolve scalability issue that causes performance degradation about about 500 concurrent requests * Code/documentation tweaks * Idle endpoint timeout task now detects idleEndpointTimeout and—unless the endpoint is found to be idle—runs tasks in the pendingAcquisitionQueue. * Updated a comment * Code tweak * Switch to HashedWheelTimer implementation for RntbdClientChannelPool.acquisitionAndIdleEndpointDetectionTimeout and revised RntbdClientChannelPool.acquireChannel. Local testing indicates that this significatnly reduces P95-P99.9 latencies * Tweaked log message * Addressed a number of threading-related issues in RntbdClientChannelPool; tweaked the RntbdReporter; and added a CsvReporter feature to the benchmark tool. They latter may be a temporary addition * Streamlined RntbdServiceEndpoint.write for performance/readability. In local testing this change resulted in a significant performance gain in these configurations: * concurrency=2048.documentCount=000001.operation=ReadLatency.operation-count=1000000 * concurrency=2048.documentCount=100000.operation=ReadLatency.operation-count=1000000 Specificallly, the P99 values moved to P99.9 and throughput increased by at least 11% as measured by (lowest[with-change] - highest[sans-change]) / highest[sans-change]) * Tweaks tested extensively--full test suite plus point read benchmarks (1 and 10,0000 documents with 2,048 concurrent requests) locally in prep for PR * Tweaked AsyncBenchmark for verifying the direct tcp “connection timeout” issue raised by T-Mobile. * Moved a misplaced statement in AsyncBenchmark that produced a lot of logger noise. * Updated version numbers in an attempt to get past CI version checks * Tweaked RntbdRequestTimer.close for readability * Removed README.md which seems to have been removed from master after being edited by me * Fixed a build issue that CI complains about. * Reverting version bump for benchmark and examples as these are in the process of being removed as libraries * Removed dead code and changed an error message in AsyncBenchmark.java * Removed merge orig files * Wired up DirectConnectionConfig to RntbdTransportClient by way of ConnectionPolicy. Also: addressed a bug in AsyncBenchmark and replaced a deprecated method call in RntbdObjectMapper. * Wired up ConnectionPolicy, DirectConnectionConfig, and RntbdTransportClient.Options * Corrected two toString methods
…Azure#11355) * Use MSAL token cache for confidential client credentials * Checkstyle: log exception * improve cert parse error * Remove force refresh for confidential client * Address Alan's feedback * Add helper to support failed completable future in java 8 * Add setter for client certificate credential builder and fix javadoc * Revert changes in azure-core for backward compatibility * Clean up HttpPipelineAdapter creation * new RuntimeException() * Simply @return docs on builders
Co-authored-by: Annie Liang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.