[CASSANDRA-4830] JdbcDate.compose is not null safe

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.1.7

Environment

Any

• Severity: Low
• Assignee: Sridharan Kuppa
• Reporter: Sridharan Kuppa

Authors

Sridharan Kuppa

Reviewers

Jonathan Ellis

• Created: 18/Oct/12 05:03
• Updated: 16/Apr/19 09:32
• Resolved: 06/Dec/12 19:23

Description

I am using the cassandra-jdbc for CQL. I have a table with timestamp column. When timestamp column is null it throws, IndexOutOfBoundsException exception since JdbcDate.compose calls the new Date(ByteBufferUtil.toLong(value)). The ByteBufferUtil.toLong(bytes) throws exception the exception since position and limit pointers are same (similar to null). This has to be handled gracefully in the JdbcDate.compose method instead of throwing exception. I would like to see implementation something like,

public Date compose(ByteBuffer bytes)
{
if(bytes.limit() - bytes.position() > 0)

{ return new Date(ByteBufferUtil.toLong(bytes)); }

return null;
}

BTW, this matches exactly reverse with decompose method. Logically it supposed to be implemented in the first place