cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-66) get_column throws exception on missing column
Date Wed, 22 Apr 2009 16:23:47 GMT


Jonathan Ellis commented on CASSANDRA-66:

1. disagree; the point is to let the thrift layer handle it for consistency (just like it
would any other RuntimeException that the code encountered).  of course the other way to be
consistent would be to add try/catch (RuntimeException) to all the methods which is nasty
boilerplate.  let the generated code do boilerplate, that's what it's for.

2. in an ideal world, I agree, but I have submitted patches to thrift before and the mean
time to review is probably multiple weeks.

> get_column throws exception on missing column
> ---------------------------------------------
>                 Key: CASSANDRA-66
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.3
>         Attachments: 0001-move-CF-checking-into-CassandraServer.-begin-to-exp.patch,
0002-return-empty-lists-instead-of-raising-an-error-where.patch, 0002-v2.patch, libthrift.jar
> get_column() throws a TException when a column is missing. It should throw a special
exception (e.g, ColumnMissingException) to distinguish this case from a real failure.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message