Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <309397419.1240863570951.JavaMail.jira@brutus>
Date: Mon, 27 Apr 2009 13:19:30 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Resolved: (AVRO-9) restrict map keys to strings
In-Reply-To: <1139100469.1239652335252.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AVRO-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting resolved AVRO-9.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 1.0
         Assignee: Sharad Agarwal

I just committed this.  Thanks, Sharad!

> restrict map keys to strings
> ----------------------------
>
>                 Key: AVRO-9
>                 URL: https://issues.apache.org/jira/browse/AVRO-9
>             Project: Avro
>          Issue Type: Improvement
>          Components: spec
>            Reporter: Doug Cutting
>            Assignee: Sharad Agarwal
>             Fix For: 1.0
>
>         Attachments: AVRO-9-py.patch, AVRO-9.patch
>
>
> In many scripting languages, the standard map datastructure does not support arbitrary keys, but rather only strings and possibly numeric values.  To simplify integration with such languages, Avro should restrict map keys to be strings.  Thus, effectively, maps would become dynamic records, records whose field names vary from instance to instance.

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