[
https://issues.apache.org/jira/browse/PHOENIX-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023339#comment-15023339
]
ASF GitHub Bot commented on PHOENIX-1674:
-----------------------------------------
Github user samarthjain commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/133#discussion_r45677553
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/util/ServerUtil.java ---
@@ -66,7 +67,9 @@ public static IOException createIOException(String msg,
Throwable t) {
} else if (t instanceof IOException) {
// If the IOException does not wrap any exception, then bubble
it up.
Throwable cause = t.getCause();
- if (cause == null || cause instanceof IOException) {
+ if (cause instanceof RetriesExhaustedWithDetailsException)
--- End diff --
I don't see code changes that are now throwing this exception. Is this
needed?
> Snapshot isolation transaction support through Tephra
> -----------------------------------------------------
>
> Key: PHOENIX-1674
> URL: https://issues.apache.org/jira/browse/PHOENIX-1674
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
> Labels: SFDC
>
> Tephra (http://tephra.io/ and https://github.com/caskdata/tephra) is one
> option for getting transaction support in Phoenix. Let's use this JIRA to
> discuss the way in which this could be integrated along with the pros and
> cons.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
