Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modified to handle errors during read path #143

Merged
merged 3 commits into from
Mar 21, 2017

Conversation

parekuti
Copy link
Contributor

Related to issue: No error is displayed when cassandra nodes are down for read path #120

Copy link
Member

@velvia velvia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good in general, just comment on wrapping the errors. So this solves the silent error problem? I'm a bit intrigued because normally exceptions bubble up automatically.

@@ -20,6 +20,7 @@ object Util {
if (resultSet.wasApplied) Success else notAppliedResponse
}.recover {
case e: DriverException => throw StorageEngineException(e)
case e: Exception => throw e
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should still wrap the error in StorageEngineException.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@@ -30,6 +31,7 @@ object Util {
// from invalid Enum strings, which should never happen, or some other parsing error
case e: NoSuchElementException => throw MetadataException(e)
case e: IllegalArgumentException => throw MetadataException(e)
case e: Exception => throw e
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, wrap in StorageEngineException

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@parekuti
Copy link
Contributor Author

Added this general exception to handle just in case of other errors than DriverException. But this is not the code actually solving the issue. The changes made to the ChunkRowMap table helped to throw exception back to the client.

Copy link
Member

@velvia velvia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@velvia velvia merged commit 28635b1 into filodb:dse-4.8-spark-1.4 Mar 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants