Return-Path: X-Original-To: apmail-avro-user-archive@www.apache.org Delivered-To: apmail-avro-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7A7F6102C1 for ; Fri, 23 Aug 2013 14:49:01 +0000 (UTC) Received: (qmail 37538 invoked by uid 500); 23 Aug 2013 14:48:59 -0000 Delivered-To: apmail-avro-user-archive@avro.apache.org Received: (qmail 37202 invoked by uid 500); 23 Aug 2013 14:48:55 -0000 Mailing-List: contact user-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@avro.apache.org Delivered-To: mailing list user@avro.apache.org Received: (qmail 36809 invoked by uid 99); 23 Aug 2013 14:48:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Aug 2013 14:48:54 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [74.125.245.70] (HELO na3sys010aog101.obsmtp.com) (74.125.245.70) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 23 Aug 2013 14:48:48 +0000 Received: from mail-ee0-f45.google.com ([74.125.83.45]) (using TLSv1) by na3sys010aob101.postini.com ([74.125.244.12]) with SMTP ID DSNKUhd2J65euazkkfUDpQMHLqpNkpmX1eAD@postini.com; Fri, 23 Aug 2013 07:48:28 PDT Received: by mail-ee0-f45.google.com with SMTP id c50so336263eek.32 for ; Fri, 23 Aug 2013 07:48:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=me8BxVktZxxl9ziqDPy+ibALBM+nzuz7rAkI5A/McMI=; b=UPgf75EKl6Hl8ONhTykZtBnDg6tXtLWI001bHtvDPqMyqj30o27+90UW1zF2RhPhBN p92jWm86W2vft48SOy3BsxHP/0NneRtPWUjAidT8tbGlmC123YTVT9+OpB0V5KJxtnux /h/kLRdYOY1MXjEBcJ9Vs4av5LLGdJkKlDxWN2Q7t/S9dqu9sErKRjk9sCkaOI7OYloq WNeiYn9uvuz4R4yHb3qgxcDK2M4z2/Gd4DVxs/zjl9BxO5PTSjqLroWIyPyIqTqgE1QN ZYmhaZYkCCj6rbZaIreII8UrrO2Cq/5L+YKJCs3fPTCzIeb2BgBeHyl0dFO3qV5P3H+y ECtA== X-Gm-Message-State: ALoCoQkm0LrvpvYTBhdfszbpfz90OaN9GMqwqijxUjxJtyKRuGPEMt3GCeKBlPRIH4/TTtcBTrVBU6U9y/PcQAi0V7RMw4+kx55oKRsGR9qt/tXAvUtVCmYqSaBq9vUAtha/m0+xmY79JbVjnpIMiyg16TEp3hLsKtsqWnfQqYLDukh/0RplMfM= X-Received: by 10.14.111.9 with SMTP id v9mr132594eeg.35.1377269286533; Fri, 23 Aug 2013 07:48:06 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.14.111.9 with SMTP id v9mr132587eeg.35.1377269286455; Fri, 23 Aug 2013 07:48:06 -0700 (PDT) Received: by 10.14.151.71 with HTTP; Fri, 23 Aug 2013 07:48:06 -0700 (PDT) Date: Fri, 23 Aug 2013 10:48:06 -0400 Message-ID: Subject: Avro data type for datetimes? From: Andrew Pennebaker To: Avro Users Content-Type: multipart/alternative; boundary=089e01682090946e8204e49e7e31 X-Virus-Checked: Checked by ClamAV on apache.org --089e01682090946e8204e49e7e31 Content-Type: text/plain; charset=ISO-8859-1 Could there be an Avro data type for date times? That would greatly increase data compatibility between systems, reducing errors from string printing and parsing, and relaxing the need for producers and consumers to agree on specific formatters. --089e01682090946e8204e49e7e31 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Could there be an Avro data type for date times? That woul= d greatly increase data compatibility between systems, reducing errors from= string printing and parsing, and relaxing the need for producers and consu= mers to agree on specific formatters.
--089e01682090946e8204e49e7e31--