Back to bug 796965
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Van Halbert | 2012-03-05 17:46:19 UTC | Group | redhat, qa, devel | |
| CC | vhalbert | |||
| Flags | needinfo?(mshirley) | |||
| Len DiMaggio | 2012-03-16 16:22:14 UTC | CC | ldimaggi | |
| Type | --- | Feature Request | ||
| Van Halbert | 2012-07-05 16:15:20 UTC | Link ID | JBoss Issue Tracker PRODMGT-145 | |
| Van Halbert | 2012-10-08 13:41:00 UTC | Link ID | JBoss Issue Tracker TEIID-2248 | |
| Van Halbert | 2013-01-24 13:51:12 UTC | Target Release | --- | FUTURE |
| Component | EDS | EDS | ||
| Version | 5.2.0 GA | 6.0.0 GA | ||
| Product | JBoss Enterprise SOA Platform 5 | JBoss Enterprise SOA Platform 6 | ||
| Van Halbert | 2013-02-06 21:27:50 UTC | Group | redhat, qa, devel | |
| Target Release | FUTURE | --- | ||
| Component | EDS | Teiid | ||
| Version | 6.0.0 GA | 6.0.0 | ||
| Assignee | vhalbert | vhalbert | ||
| Product | JBoss Enterprise SOA Platform 6 | JBoss Data Services Platform 6 | ||
| Van Halbert | 2013-03-07 18:49:03 UTC | Status | NEW | MODIFIED |
| Target Release | --- | 6.0 | ||
| Target Milestone | --- | ER1 | ||
| Red Hat Bugzilla | 2013-03-15 04:16:27 UTC | CC | belong | |
| Doc Text | Data Services did not utilize the Salesforce Bulk API for large inserts. As a result, performance when writing large amounts of data to Salesforce was not maximized. Once integrated | |||
| Doc Text | errors will be handled as follows. If an error is reported when inserting a row in Salesforce, since the communication is ASYNC there is no way to cancel the bulk job safely | |||
| Doc Text | so the job continues and reports which rows have not been inserted. Each error is reported back to the client as an SQLWarning. From here Data Services could throw an SQlException but that will not indicate that the whole job has been aborted | |||
| Doc Text | so it will be implemented as an SQLWarning. | |||
| Doc Text | Data Services did not utilize the Salesforce Bulk API for large inserts. As a result, performance when writing large amounts of data to Salesforce was not maximized. Once integrated | Previously, Data Services has not supported bulk inserts. It is proposed that Data Services 6 will utilize the Salesforce Bulk API to support this feature. As a result, users will be able to submit multiple inserts to Salesforce in one go | ||
| Doc Text | errors will be handled as follows. If an error is reported when inserting a row in Salesforce, since the communication is ASYNC there is no way to cancel the bulk job safely | rather than submitting them one at a time. This will improve performance by reducing the number of trips between the client application and the server. | ||
| Doc Text | so the job continues and reports which rows have not been inserted. Each error is reported back to the client as an SQLWarning. From here Data Services could throw an SQlException but that will not indicate that the whole job has been aborted | |||
| Doc Text | so it will be implemented as an SQLWarning. | |||
| Doc Type | Bug Fix | Known Issue | ||
| Doc Type | Known Issue | Bug Fix | ||
| Red Hat Bugzilla | 2013-03-15 04:17:12 UTC | Doc Type | Bug Fix | Known Issue |
| Doc Type | Known Issue | Bug Fix | ||
| Red Hat Bugzilla | 2013-03-15 04:18:01 UTC | Doc Type | Bug Fix | Known Issue |
| Doc Type | Known Issue | Bug Fix | ||
| Van Halbert | 2013-07-16 14:33:09 UTC | Doc Type | Bug Fix | Enhancement |
| Red Hat Bugzilla | 2013-07-16 14:33:09 UTC | Doc Type | Enhancement | Bug Fix |
| Van Halbert | 2013-10-08 15:33:38 UTC | Doc Text | Previously, Data Services has not supported bulk inserts. It is proposed that Data Services 6 will utilize the Salesforce Bulk API to support this feature. As a result, users will be able to submit multiple inserts to Salesforce in one go | Previously, JBoss Data Virtualization has not supported bulk inserts. It is proposed that JBoss Data Virtualization 6 will utilize the Salesforce Bulk API to support this feature. As a result |
| Doc Text | , rather than submitting them one at a time. This will improve performance by reducing the number of trips between the client application and the server. | , users will be able to submit multiple inserts to Salesforce in one go, rather than submitting them one at a time. This will improve performance by reducing the number of trips between the client application and the server. | ||
| Doc Type | Bug Fix | Enhancement | ||
| Status | MODIFIED | ON_QA | ||
| Van Halbert | 2014-03-17 13:33:10 UTC | Doc Text | Previously, JBoss Data Virtualization has not supported bulk inserts. It is proposed that JBoss Data Virtualization 6 will utilize the Salesforce Bulk API to support this feature. As a result | Previously, JBoss Data Virtualization has not supported bulk inserts. JBoss Data Virtualization 6 now utilizes the Salesforce Bulk API to support this feature. As a result, users can submit multiple inserts to Salesforce in one go |
| Doc Text | , users will be able to submit multiple inserts to Salesforce in one go, rather than submitting them one at a time. This will improve performance by reducing the number of trips between the client application and the server. | , rather than submitting them one at a time. This improves performance by reducing the number of trips between the client application and the server. | ||
| Flags | needinfo?(mshirley) | |||
| Filip Elias | 2014-06-17 13:48:00 UTC | Status | ON_QA | VERIFIED |
| CC | felias | |||
| Filip Elias | 2016-02-10 08:51:44 UTC | CC | belong | |
| Keywords | QA-Closed | |||
| Status | VERIFIED | CLOSED | ||
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2016-02-10 03:51:44 UTC |
Back to bug 796965