You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ApacheConnector-README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ The SDK for Java also provides an environment variable to switch back to the old
71
71
72
72
### Switching off auto-close of streams
73
73
74
-
For API calls that return binary/stream response, the SDK will auto-close the stream once the stream has been completely read by the customer. If reading the stream completely, the SDK will automatically try to close the stream to release the connection from the connection pool, to disable this feature of auto-closing streams on full read, please call `ResponseHelper.shouldAutoCloseResponseInputStream(false)`. This is because the SDK for Java supports the Apache Connector for sending requests and managing connections to the service. By default, the Apache Connector supports connection pooling and in the cases where the stream from the response is not closed, the connections don't get released from the connection pool and in turn results in an indefinite wait time.
74
+
For API calls that return binary/stream response, the SDK will auto-close the stream once the stream has been completely read by the customer. If reading the stream completely, the SDK will automatically try to close the stream to release the connection from the connection pool, to disable this feature of auto-closing streams on full read, please call `Options.shouldAutoCloseResponseInputStream(false)`. This is because the SDK for Java supports the Apache Connector for sending requests and managing connections to the service. By default, the Apache Connector supports connection pooling and in the cases where the stream from the response is not closed, the connections don't get released from the connection pool and in turn results in an indefinite wait time.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+127Lines changed: 127 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,133 @@ All notable changes to this project will be documented in this file.
3
3
4
4
The format is based on [Keep a Changelog](http://keepachangelog.com/).
5
5
6
+
## 2.47.0 - 2022-10-25
7
+
### Added
8
+
- Support for the Disaster Recovery service
9
+
- Support for running code interactively with session applications using statements in the Data Flow service
10
+
- Support for language custom models and language translation in the AI Language service
11
+
### Breaking Changes
12
+
- Class `com.oracle.bmc.ailanguage.model.EntityDocument` has been removed in the AI Language service
13
+
- Class `com.oracle.bmc.ailanguage.model.KeyPhraseDocument` has been removed in the AI Language service
14
+
- Class `com.oracle.bmc.ailanguage.model.SentimentsDocument` has been removed in the AI Language service
15
+
- Class `com.oracle.bmc.ailanguage.model.TextClassificationDocument` has been removed in the AI Language service
16
+
17
+
## 2.46.0 - 2022-10-04
18
+
### Added
19
+
- Support for calling Oracle Cloud Infrastructure services in the eu-dcc-milan-1 region
20
+
- Support for target host identification and SOCKS support on dynamic port forwarding sessions in the Bastion service
21
+
- Support for viewing top processes running at a particular point of time in the Operations Insights service
22
+
- Support for filtering top processes by a single process to view that process's trend over time in the Operations Insights service
23
+
- Support for creating Enterprise Manager-based Windows host targets in the Operations Insights service
24
+
- Support for creating Management Agent Cloud-based Windows and Solaris host targets in the Operations Insights service
25
+
26
+
### Breaking Changes
27
+
- Method `public java.lang.Integer getTargetResourcePort()` has been removed from the model `com.oracle.bmc.bastion.model.CreateSessionTargetResourceDetails` in the Bastion Service
28
+
- Method `public java.lang.Integer getTargetResourcePort()` has been removed from the model `com.oracle.bmc.bastion.model.TargetResourceDetails` in the Bastion Service
29
+
30
+
## 2.45.0 - 2022-09-27
31
+
### Added
32
+
- Support for search capabilities for monitored resources in the Stack Monitoring service
33
+
- Support for deleting monitored resources with their members in the Stack Monitoring service
34
+
- Support for creating host-type monitored resources in the Stack Monitoring service
35
+
- Support for associating external resources during creation of monitored resources in the Stack Monitoring service
36
+
- Support for uploading bulk data in the NoSQL Database Cloud service
37
+
- Support for examining query execution plans in the NoSQL Database Cloud service
38
+
- Support for starting and stopping clusters in the Big Data service
39
+
- Support for additional compute shapes in the Big Data service
40
+
- Support for backwards pagination in the Search service
41
+
- Support for elastic compute for Exadata Cloud at Customer in the Database service
42
+
43
+
### Breaking Changes
44
+
- Support for default retries on operations of the NoSQL Database Cloud service
45
+
46
+
## 2.44.0 - 2022-09-20
47
+
### Added
48
+
- Support for the Cloud Bridge service
49
+
- Support for the Cloud Migrations service
50
+
- Support for display banners, trails, and sizes in the GoldenGate service
51
+
- Support for generic REST data assets, flattening of data in Data Flow, and runtime information on pipelines in the Data Integration service
52
+
- Support for expanded search functionality in the Threat Intelligence service
53
+
- Support for ingest-time rules and specifying logsets and query strings during recalls in the Logging Analytics service
54
+
- Support for repository mirroring from Visual Builder Studio in the DevOps service
55
+
- Support for running a managed build stage with the source code hosted in a Visual Builder Studio repository in the DevOps service
56
+
- Support for triggering a build run based on an event in a Visual Builder Studio repository in the DevOps service
57
+
- Support for additional parameters during cost management scheduling in the Usage service
58
+
59
+
### Breaking Changes
60
+
- Support for retries by default on operations of the GoldenGate service
61
+
- Support for retries by default on operations of the Threat Intelligence service
62
+
63
+
## 2.43.0 - 2022-09-13
64
+
### Added
65
+
- Support for calling Oracle Cloud Infrastructure services in the eu-madrid-1 region
66
+
- Support for exporting and importing larger model artifacts in the model catalog in the Data Science service
67
+
- Support for Request Based Authorization in the API Gateway service
68
+
- Support for Dynamic Authentication in the API Gateway service
69
+
- Support for Dynamic Routing Backend in the API Gateway service
70
+
71
+
### Breaking Changes
72
+
- Support for retries by default on some operations of the Data Science service
73
+
74
+
## 2.42.0 - 2022-09-06
75
+
### Added
76
+
- Support for generic REST, OCI Streaming service, and Lake House connectors in the Data Connectivity Management service
77
+
- Support for connecting to the Data Catalog service in the Data Connectivity Management service
78
+
- Support for Kerberos and SSL for HDFS operations in the Data Connectivity Management service
79
+
- Support for excel-formatted data and default columns in the Data Connectivity Management service
80
+
- Support for reporting connector usage in the Data Connectivity Management service
81
+
- Support for preferred credentials for performing privileged operations in the Database Management service
82
+
- Support for passing a content encoding when posting metrics in the Monitoring service
83
+
84
+
### Breaking Changes
85
+
- Support for retries by default on some operations of the Data Connectivity Management service
86
+
- Method `public com.oracle.bmc.dataconnectivity.responses.DeleteConnectionValidationResponse deleteConnectionValidation(com.oracle.bmc.dataconnectivity.requests.DeleteConnectionValidationRequest)` has been removed from `com.oracle.bmc.dataconnectivity.DataConnectivityManagement` in the Data Connectivity Management service
87
+
- Method `public com.oracle.bmc.dataconnectivity.responses.GetConnectionValidationResponse getConnectionValidation(com.oracle.bmc.dataconnectivity.requests.GetConnectionValidationRequest)` has been removed from `com.oracle.bmc.dataconnectivity.DataConnectivityManagement` in the Data Connectivity Management service
88
+
- Method `public com.oracle.bmc.dataconnectivity.responses.ListConnectionValidationsResponse listConnectionValidations(com.oracle.bmc.dataconnectivity.requests.ListConnectionValidationsRequest)` has been removed from `com.oracle.bmc.dataconnectivity.DataConnectivityManagement` in the Data Connectivity Management service
89
+
- Method `public java.lang.Iterable listConnectionValidationsRecordIterator(com.oracle.bmc.dataconnectivity.requests.ListConnectionValidationsRequest)` has been removed from `com.oracle.bmc.dataconnectivity.DataConnectivityManagementPaginators` in the Data Connectivity Management service
90
+
- Method `public java.lang.Iterable listConnectionValidationsResponseIterator(com.oracle.bmc.dataconnectivity.requests.ListConnectionValidationsRequest)` has been removed from `com.oracle.bmc.dataconnectivity.DataConnectivityManagementPaginators` in the Data Connectivity Management service
91
+
- Class `com.oracle.bmc.dataconnectivity.model.ConnectionValidationSummaryCollection` has been removed in the Data Connectivity Management service
92
+
- Class `com.oracle.bmc.dataconnectivity.requests.DeleteConnectionValidationRequest` has been removed in the Data Connectivity Management service
93
+
- Class `com.oracle.bmc.dataconnectivity.requests.GetConnectionValidationRequest` has been removed in the Data Connectivity Management service
94
+
- Class `com.oracle.bmc.dataconnectivity.requests.ListConnectionValidationsRequest` has been removed in the Data Connectivity Management service
95
+
- Class `com.oracle.bmc.dataconnectivity.requests.ListConnectionValidationsRequest$SortBy` has been removed in the Data Connectivity Management service
96
+
- Class `com.oracle.bmc.dataconnectivity.requests.ListConnectionValidationsRequest$SortOrder` has been removed in the Data Connectivity Management service
97
+
- Method `public java.lang.String getResourceId()` has been removed from `com.oracle.bmc.dataconnectivity.requests.ListWorkRequestsRequest` in the Data Connectivity Management service
98
+
- Class `com.oracle.bmc.dataconnectivity.responses.DeleteConnectionValidationResponse` has been removed in the Data Connectivity Management service
99
+
- Class `com.oracle.bmc.dataconnectivity.responses.GetConnectionValidationResponse` has been removed in the Data Connectivity Management service
100
+
- Return type of method `public java.lang.Float getRetryAfter()` has been changed to `java.lang.Integer` in the response `com.oracle.bmc.dataconnectivity.responses.GetWorkRequestResponse` in the Data Connectivity Management service
101
+
- Class `com.oracle.bmc.dataconnectivity.responses.ListConnectionValidationsResponse` has been removed in the Data Connectivity Management service
102
+
103
+
## 2.41.1 - 2022-08-30
104
+
### Added
105
+
- Support for opting out of guest VM event collection, health metrics, diagnostics logs, and traces in the Database service
106
+
- Support for in-place upgrades for software-defined data centers in the VMWare Solution service
107
+
- Support for single-client access name protocol as a data source for private access channels in the Analytics Cloud service
108
+
- Support for network security groups, egress control on public datasources, and GitHub access in the Analytics Cloud service
109
+
- Support for performance-based autotuning of block and boot volumes in the Block Storage service
110
+
111
+
## 2.41.0 - 2022-08-23
112
+
### Added
113
+
- Support for the Enterprise Manager Warehouse service
114
+
- Support for additional configuration variables in the MySQL Database service
115
+
- Support for file filters in the DevOps service
116
+
- Support for support rewards redemption summaries in the Usage service
117
+
- Support for the parent tenancy of an organization to view child tenancy categories, recommendations, and resource actions in the Optimizer service
118
+
- Support for choosing prior versions during infrastructure maintenance on Exadata Cloud at Customer in the Database service
119
+
120
+
### Breaking Changes
121
+
- Class `com.oracle.bmc.emwarehouse.EmDataLake` has been removed in the Enterprise Manager Warehouse service
122
+
- Class `com.oracle.bmc.emwarehouse.EmDataLakeClient$Builder` has been removed in the Enterprise Manager Warehouse service
123
+
- Class `com.oracle.bmc.emwarehouse.EmDataLakePaginators` has been removed in the Enterprise Manager Warehouse service
124
+
- Class `com.oracle.bmc.emwarehouse.EmDataLakeWaiters` has been removed in the Enterprise Manager Warehouse service
125
+
- Return type of method `public java.lang.Integer getCteMaxRecursionDepth()` has been changed to `java.lang.Long` in the model `com.oracle.bmc.mysql.model.ConfigurationVariables` in the MySQL Database service
126
+
- Return type of method `public java.lang.Integer getInnodbFtResultCacheLimit()` has been changed to `java.lang.Long` in the model `com.oracle.bmc.mysql.model.ConfigurationVariables` in the MySQL Database service
127
+
- Return type of method `public java.lang.Integer getInnodbMaxPurgeLag()` has been changed to `java.lang.Long` in the model `com.oracle.bmc.mysql.model.ConfigurationVariables` in the MySQL Database service
128
+
- Return type of method `public java.lang.Integer getMaxExecutionTime()` has been changed to `java.lang.Long` in the model `com.oracle.bmc.mysql.model.ConfigurationVariables` in the MySQL Database service
129
+
- Return type of method `public java.lang.Integer getParserMaxMemSize()` has been changed to `java.lang.Long` in the model `com.oracle.bmc.mysql.model.ConfigurationVariables` in the MySQL Database service
130
+
- Return type of method `public java.lang.Integer getQueryAllocBlockSize()` has been changed to `java.lang.Long` in the model `com.oracle.bmc.mysql.model.ConfigurationVariables` in the MySQL Database service
131
+
- Return type of method `public java.lang.Integer getQueryPreallocSize()` has been changed to `java.lang.Long` in the model `com.oracle.bmc.mysql.model.ConfigurationVariables` in the MySQL Database service
132
+
6
133
## 2.40.0 - 2022-08-16
7
134
### Added
8
135
- Support for Logging Analytics as a streaming source target in the Service Connector Hub service
@@ -81,7 +80,7 @@ If the request to the server hangs for an indefinite time and the program gets s
81
80
because the connection is not released from the Apache connection
82
81
pool. If you're calling APIs that return a binary/stream response,
83
82
please make sure to close all the streams returned from the response to release the connections from the connection pool in case of partial reads. If reading the stream completely, the SDK will
84
-
automatically try to close the stream to release the connection from the connection pool, to disable this feature of auto-closing streams on full read, please call `ResponseHelper.shouldAutoCloseResponseInputStream(false)`. This is because the SDK for Java supports the Apache Connector for sending requests and managing connections to the service. By default, the Apache Connector supports connection pooling and in the cases where the stream from the response is not closed, the connections don't get released from the connection pool and in turn results in an indefinite wait time. This can be avoided either by closing the streams or switching back to the Jersey default connector, i.e. `HttpUrlConnector`. You can find more information about the same in the OCI Java SDK Troubleshooting section.
83
+
automatically try to close the stream to release the connection from the connection pool, to disable this feature of auto-closing streams on full read, please call `Options.shouldAutoCloseResponseInputStream(false)`. This is because the SDK for Java supports the Apache Connector for sending requests and managing connections to the service. By default, the Apache Connector supports connection pooling and in the cases where the stream from the response is not closed, the connections don't get released from the connection pool and in turn results in an indefinite wait time. This can be avoided either by closing the streams or switching back to the Jersey default connector, i.e. `HttpUrlConnector`. You can find more information about the same in the OCI Java SDK Troubleshooting section.
85
84
86
85
### Performance issues and switching between connection closing strategies with the Apache Connector
0 commit comments