[IGNITE-6125] Improve robustness for JDBC driver metadata queries

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.3
• Component/s: jdbc
• Assignee: Ilya Kasnacheev
• Reporter: Ilya Kasnacheev
• Created: 21/Aug/17 10:27
• Updated: 30/Aug/17 13:23
• Resolved: 30/Aug/17 13:22

Description

org.apache.ignite.internal.jdbc2.JdbcDatabaseMetadata is in worrysome state:

• Makes frivolous use of toUpperCase() to address former.
• getPrimaryKeys() never returns anything because of defective use of toUpperCase().
• No tests on indexes, primary keys, schemas or parameters metadata retrieval.
• Ignores "catalog" parameter instead of checking if it matches empty catalog.
• See also IGNITE-6138, IGNITE-6139

That should be fixes without compromising backwards compatibility too much. Tests may be borrowed from thin client implementation.

Issue Links

• is related to: IGNITE-4643 JdbcDatabaseMetadata.getIndexInfo() method not working
• relates to: IGNITE-6138 JDBC driver metadata queries operate on cache/type instead of schema/table
• relates to: IGNITE-6139 JDBC driver should return actual values for get*Version()
• relates to: IGNITE-6187 Cache JdbcDatabaseMetadata in JdbcConnection
• links to: GitHub Pull Request #2506