Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Critical |
| Complexity | Unknown |
| Component | Q Analyzer - Grid Results |
| Version | 16.0 |
In Vertica, an INT / INTEGER data type is the size of a BIGINT. AFTableColumnInitVertica.java Line 114 shows that the INTEGER datatype is an Integer.class, but it should be a Long.class since in Vertica the INTEGER datatype is the size of a BIGINT.
INTEGER, INT, INT8, TINYINT, SMALLINT, BIGINT are all bigint datatypes. I have made the needed changes to the vertica init class. I believe the issue above though has more to do with vertica driver specific issues. I am trying to narrow it down. I will check in these changes and test against vertica drivers 6.0, 6.1, 7.0 & 7.1 using the binaries. I am having a hard time reproducing the issue from source...
INTEGER, INT, INT8, TINYINT, SMALLINT, BIGINT are all bigint datatypes. I have made the needed changes to the vertica init class. I believe the issue above though has more to do with vertica driver specific issues. I am trying to narrow it down. I will check in these changes and test against vertica drivers 6.0, 6.1, 7.0 & 7.1 using the binaries. I am having a hard time reproducing the issue from source...
all driver versions will work correctly now. You may use the below create table and insert statements to test.
all driver versions will work correctly now. You may use the below create table and insert statements to test.
Issue #13280 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 16.0.4-8 |
| No time estimate |
In Vertica, an INT / INTEGER data type is the size of a BIGINT. AFTableColumnInitVertica.java Line 114 shows that the INTEGER datatype is an Integer.class, but it should be a Long.class since in Vertica the INTEGER datatype is the size of a BIGINT.