[BUG] getMetaData().getColumns() returns duplicate columns #1748

Activity

1. eric-wang-1990

   added the

   Bug

   issue type on Oct 26, 2026
2. eric-wang-1990

   added

   engineer-botMaintainer-only: triggers the autonomous engineer-bot (bug-fix author on issues; follow-up on PRs)Maintainer-only: triggers the autonomous engineer-bot (bug-fix author on issues; follow-up on PRs)

   on Oct 26, 2026
3. peco-engineer-bot commented on Oct 27, 2026

   

   peco-engineer-botBot

   on Oct 27, 2026 – with Peco Engineer Bot

   Contributor

   More actions

   🤖 engineer-bot could not complete an automated fix. See the workflow run for details.
4. rahuls-db commented on Oct 28, 2026

   

   rahuls-db

   on Oct 28, 2026

   Collaborator

   More actions

   Hey @alitaker , We attempted to reproduce this using a table created with DEEP CLONE and consumed the complete getColumns() result using while (rs.next()), but did not observe duplicates.
   Can you share a standalone Java file that we can run directly to reproduce the issue, along with the exact JDBC driver artifact used? Please remove any credentials.
5. alitaker commented on Oct 30, 2026

   

   alitaker

   on Oct 30, 2026

   Last edited by alitaker

   Author

   More actions

   Unfortunately I'm not the owner of the database and cannot run DEEP CLONE copies.
   The columns are of this kind:

   {'col_name': '_0002', 'data_type': 'varchar(7)'}, 
   {'col_name': '_0003', 'data_type': 'varchar(1)'}, 
   {'col_name': '_0008', 'data_type': 'varchar(1)'}, 
   {'col_name': '_0009', 'data_type': 'varchar(1)'}, 
   {'col_name': '_0010', 'data_type': 'varchar(7)'}
   ]
   

   The driver version was:

   		<dependency>
   			<groupId>com.databricks</groupId>
   			<artifactId>databricks-jdbc</artifactId>
   			<version>2.6.40-patch-1</version>
   		</dependency>
   

   Then I compiled the latest jdk-8 branch (3.4.4) from the repo, but the result didn't change.
6. rahuls-db commented on Nov 2, 2026

   

   rahuls-db

   on Nov 2, 2026

   Collaborator

   More actions

   Unfortunately, this doesn’t help me reproduce the issue. I’ve already tried the jdk-8 branch, and it appears to work as expected. If you can share a standalone repro, or ask someone else to provide one, that would help me investigate further. Otherwise, I’ll need to close this as not reproducible.
7. alitaker commented on Nov 2, 2026

   

   alitaker

   on Nov 2, 2026

   Author

   More actions

   @rahuls-db, thanx for putting all that effort in reproducing the issue.
   Unfortunately the server is on a private network on Azure and data cannot be exported for policy.
   You may close the issue. I used a workaround that filters duplicate column names for now.
8. alitaker

   closed this as completedon Nov 2, 2026