Back to bug 896305
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Eiichi Nagai | 2013-01-17 01:19:15 UTC | Comment 0 is private | 1 | 0 |
| Van Halbert | 2013-01-24 14:19:29 UTC | Group | redhat | |
| CC | soa-p-jira | |||
| Component | doc-Teiid_Designer_User_Guide | doc-Data_Services_Reference_Guide | ||
| Flags | needinfo?(vhalbert) | |||
| Status | NEW | CLOSED | ||
| Resolution | --- | NOTABUG | ||
| Flags | needinfo?(vhalbert) | |||
| Last Closed | 2013-01-21 18:52:48 UTC | |||
| Status | CLOSED | ASSIGNED | ||
| Component | doc-Data_Services_Reference_Guide | EDS | ||
| Resolution | NOTABUG | --- | ||
| Assignee | belong | vhalbert | ||
| Keywords | Reopened | |||
| CC | vhalbert | |||
| Van Halbert | 2013-02-01 13:49:05 UTC | Link ID | JBoss Issue Tracker TEIID-2361 | |
| Van Halbert | 2013-02-01 13:52:36 UTC | Status | ASSIGNED | MODIFIED |
| Component | EDS | EDS | ||
| Version | 5.3.0 GA | unspecified | ||
| Assignee | vhalbert | vhalbert | ||
| Product | JBoss Enterprise SOA Platform 5 | JBoss Enterprise SOA Platform 6 | ||
| Van Halbert | 2013-02-01 13:52:54 UTC | Target Release | --- | 6.0.0 GA |
| Van Halbert | 2013-02-07 22:56:54 UTC | Group | redhat | |
| Target Release | 6.0.0 GA | 6.0 | ||
| Component | EDS | Teiid | ||
| Assignee | vhalbert | vhalbert | ||
| Product | JBoss Enterprise SOA Platform 6 | JBoss Data Services Platform 6 | ||
| Target Milestone | --- | ER1 | ||
| Hisanobu Okuda | 2013-02-22 05:37:51 UTC | CC | hokuda | |
| Len DiMaggio | 2013-06-27 19:44:55 UTC | CC | belong | |
| Doc Text | Users noticed that the default MAX String size was set to 4000 | |||
| Doc Text | but that larger values were sometimes required and worked without any trouble. The proposed fix is to increase the default MAX String size to 16k and to allow it to be adjusted for larger sizes. Data Services will try to truncate in-memory strings to the | |||
| Doc Text | MAX size; however, it will remain as a recommended maximum rather than a strict one, enabling some simple pass-through scenarios for sources that do not compare direct string values against the maximum. | |||
| CC | ldimaggi | |||
| Van Halbert | 2013-07-16 14:38:49 UTC | Version | unspecified | 6.0.0 |
| Van Halbert | 2013-10-08 15:39:41 UTC | Doc Text | Users noticed that the default MAX String size was set to 4000 | Users noticed that the default MAX String size was set to 4000 |
| Doc Text | , but that larger values were sometimes required and worked without any trouble. The proposed fix is to increase the default MAX String size to 16k and to allow it to be adjusted for larger sizes. Data Services will try to truncate in-memory strings to | , but that larger values were sometimes required and worked without any trouble. The proposed fix is to increase the default MAX String size to 16k and to allow it to be adjusted for larger sizes. JBoss Data Virtualization will try to truncate in-memory | ||
| Doc Text | the MAX size; however, it will remain as a recommended maximum rather than a strict one, enabling some simple pass-through scenarios for sources that do not compare direct string values against the maximum. | strings to the MAX size; however, it will remain as a recommended maximum rather than a strict one, enabling some simple pass-through scenarios for sources that do not compare direct string values against the maximum. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Status | MODIFIED | ON_QA | ||
| Filip Nguyen | 2014-02-11 13:03:53 UTC | Doc Text | Users noticed that the default MAX String size was set to 4000 | Users noticed that the default MAX String size was set to 4000 |
| Doc Text | , but that larger values were sometimes required and worked without any trouble. The proposed fix is to increase the default MAX String size to 16k and to allow it to be adjusted for larger sizes. JBoss Data Virtualization will try to truncate in-memory | , but that larger values were sometimes required and worked without any trouble. The solution was to increase the default MAX String size to 16k and to allow it to be adjusted for larger sizes. JBoss Data Virtualization will try to truncate in-memory | ||
| Doc Text | strings to the MAX size; however, it will remain as a recommended maximum rather than a strict one, enabling some simple pass-through scenarios for sources that do not compare direct string values against the maximum. | strings to the MAX size; however, it will remain as a recommended maximum rather than a strict one, enabling some simple pass-through scenarios for sources that do not compare direct string values against the maximum. | ||
| Status | ON_QA | VERIFIED | ||
| CC | fnguyen | |||
| Van Halbert | 2014-03-10 20:42:13 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2013-01-21 18:52:48 UTC | 2014-03-10 16:42:13 UTC |
Back to bug 896305