[MCOL-1213] SystemCatalog.getTable("table name") doesn't support uppercase letters Created: 2018-02-12 Updated: 2023-10-26 Resolved: 2018-03-22 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.1.2 |
| Fix Version/s: | 1.1.4 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jens Röwekamp (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Python, Java, C++ not tested |
||
| Issue Links: |
|
||||||||
| Sprint: | 2018-05, 2018-06 | ||||||||
| Description |
|
Using SystemCatalogTable.getColumn(columnName) fails if using a column name with uppercase letters like "helloWorld". Using the lowercase name works. Tested in Python and Java. Same issue for SystemCatalog.getTable(tableName) To reproduce: In mcsmysql:
In Python:
|
| Comments |
| Comment by Jens Röwekamp (Inactive) [ 2018-02-13 ] |
|
Also the same for ColumnStoreSystemCatalogColumn.getColumnName(), returns only the lower case column name even though a column shows upper case letters in mcsmysql. |
| Comment by Andrew Hutchings (Inactive) [ 2018-03-08 ] |
|
ColumnStore's System Catalogue only stores the names in lowercase so we should make matches case insensitive and document accordingly. |
| Comment by Andrew Hutchings (Inactive) [ 2018-03-08 ] |
|
Patch makes getTable and getColumn case insensitive. Also updates the documentation to point out that system catalog is lower case. For QA: system catalog test in API's build-in regression suite updated for this. |
| Comment by Daniel Lee (Inactive) [ 2018-03-22 ] |
|
Build verified: 1.1.4-1 source /root/columnstore/mariadb-columnstore-server Merge pull request #104 from mariadb-corporation/davidhilldallas-patch-3 update version /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine Merge pull request #427 from mariadb-corporation/ Mcol 1225 - fix mysql/lib library path commit 8f4f304e22c8629e6b5feb0bb9724b09ae89b787 Merge pull request #61 from mariadb-corporation/1.1-mergeup-20180322 Merge develop-1.1 into develop Reproduced the issue in 1.1.3-1 and verified the fix in 1.1.4-1 source above. Spent time on getting the build environment updated |