[CALCITE-4503] Order of fields in records should follow that of the SQL types

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.17.0
• Fix Version/s: avatica-1.18.0
• Component/s: avatica
• Labels: pull-request-available
• Assignee: Alessandro Solimando
• Reporter: Alessandro Solimando
• Created: 18/Feb/21 08:00
• Updated: 18/May/21 11:23
• Resolved: 07/Apr/21 17:17

Description

When dealing with records coming from Java classes, Avatica relies on the order of fields coming from java.lang.Class#getFields instead of using the order defined in the underlying SQL data type:

1. org.apache.calcite.avatica.MetaImpl#createGetter(int ordinal)
2. org.apache.calcite.avatica.util.RecordIteratorCursor#RecordIteratorCursor(Iterator<E> iterator, Class<E> clazz)

This behaviour prevents the change of fields orders, and it's particularly problematic because #getFields is JVM-specific.

 

Issue Links

• is related to: CALCITE-4556 CalciteMetaImpl#createEmptyResultSet override of (Avatica) MetaImpl#createEmptyResultSet should not pass a class instance to CursorFactory#deduce
• relates to: CALCITE-2489 Order of fields in JavaTypeFactoryImpl#createStructType is unstable