Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 85166 invoked from network); 10 Mar 2009 09:15:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Mar 2009 09:15:15 -0000 Received: (qmail 36076 invoked by uid 500); 10 Mar 2009 09:15:12 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 36066 invoked by uid 500); 10 Mar 2009 09:15:12 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 36055 invoked by uid 99); 10 Mar 2009 09:15:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Mar 2009 02:15:11 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Mar 2009 09:15:10 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A538B234C004 for ; Tue, 10 Mar 2009 02:14:50 -0700 (PDT) Message-ID: <1350710868.1236676490675.JavaMail.jira@brutus> Date: Tue, 10 Mar 2009 02:14:50 -0700 (PDT) From: "Klaas Bosteels (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Created: (HADOOP-5450) Add support for application-specific typecodes to typed bytes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Add support for application-specific typecodes to typed bytes ------------------------------------------------------------- Key: HADOOP-5450 URL: https://issues.apache.org/jira/browse/HADOOP-5450 Project: Hadoop Core Issue Type: Improvement Components: contrib/streaming Reporter: Klaas Bosteels Assignee: Klaas Bosteels For serializing objects of types that are not supported by typed bytes serialization, applications might want to use a custom serialization format. Right now, typecode 0 has to be used for the bytes resulting from this custom serialization, which could lead to problems when deserializing the objects because the application cannot know if a byte sequence following typecode 0 is a customly serialized object or just a raw sequence of bytes. Therefore, a range of typecodes that are treated as aliases for 0 should be added, such that different typecodes can be used for application-specific purposes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.