[ https://issues.apache.org/jira/browse/DRILL-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Westin updated DRILL-2603: -------------------------------- Assignee: Daniel Barclay (Drill) > Review, resolve NULL checks/isNull()/null around vectors, accessors, JDBC > SQLAccessor, etc. > ------------------------------------------------------------------------------------------- > > Key: DRILL-2603 > URL: https://issues.apache.org/jira/browse/DRILL-2603 > Project: Apache Drill > Issue Type: Task > Components: Execution - Data Types > Reporter: Daniel Barclay (Drill) > Assignee: Daniel Barclay (Drill) > Fix For: 1.0.0 > > > Review the checking for SQL NULL and mapping to Java null (for non-primitive > types) from the vector and vector access layer up through the JDBC layer > (e.g., SQLAccessors (which is just for JDBC)), resolve where checking should > be done, and specify that contract information in the Javadoc documentation. > Considerations: > - With DRILL-2463, there are now some redundant checks for SQL NULL. > - Get methods returning non-primitive types must follow a different pattern, > since they can't return Java null. > - Behavior that is very specific to JDBC usually should be implemented in the > JDBC layer. (For example, JDBC's NULL-reporting protocol of calling > getInt(...) and then calling wasNull() shouldn't appear in lower layers > (e.g., the planned DrillClient-level public interface) unless we > intentionally choose that protocol for there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)