[PHOENIX-5994] SqlAlchemy schema filtering incorrect semantics

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: queryserver-6.0.0
• Fix Version/s: queryserver-6.0.0
• Component/s: queryserver
• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 07/Jul/20 11:19
• Updated: 03/Aug/21 08:35
• Resolved: 16/Jul/20 03:43

Description

The SqlAlchemy driver interprets the schema=None parameter as any/all schema.
According to the SqlAlchemy docs this should mean default schema.

Issue Links

• is related to: PHOENIX-6003 Metadata operations via Avatica turn empty string args to null
• is related to: PHOENIX-6004 Metadata operations cannot filter on case-sensitive names
• links to: GitHub Pull Request #42