[
https://issues.apache.org/jira/browse/CASSANDRA-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-4830:
--------------------------------------
Reviewer: jbellis
Priority: Trivial (was: Major)
Affects Version/s: (was: 1.1.5)
1.0.0
Fix Version/s: 1.1.7
Assignee: Sridharan Kuppa
done in 9d7ba39cbb6f93759f654c7df1771b52354dec36, thanks!
> JdbcDate.compose is not null safe
> ---------------------------------
>
> Key: CASSANDRA-4830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4830
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Environment: Any
> Reporter: Sridharan Kuppa
> Assignee: Sridharan Kuppa
> Priority: Trivial
> Fix For: 1.1.7
>
>
> 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 ;)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
