Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Message-ID: <19200047.50641276287555305.JavaMail.jira@thor>
Date: Fri, 11 Jun 2010 16:19:15 -0400 (EDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Subject: [jira] Commented: (AVRO-573) Need to include Handshake Response
 when handling a system error on the Java server side
In-Reply-To: <15617334.39461276233376298.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AVRO-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877951#action_12877951 ] 

Doug Cutting commented on AVRO-573:
-----------------------------------

I don't think a match=ERROR should be required to include the server's protocol or hash.
Imagine a misconfigured server that cannot manage to locate its protocol for, e.g., a requested URL.
Ideally this might throw an HTTP error, but it might also result in an NPE within Avro.
It'd be nice if a client didn't hang or fail strangely in such cases.

We should probably specify a metadata key for an error message.  Does that sound reasonable?

> Need to include Handshake Response when handling a system error on the Java server side
> ---------------------------------------------------------------------------------------
>
>                 Key: AVRO-573
>                 URL: https://issues.apache.org/jira/browse/AVRO-573
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>            Reporter: Jeff Hammerbacher
>             Fix For: 1.4.0
>
>
> System error is not handling everything right now. Details in the comments.

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