Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A4E3F17419 for ; Tue, 6 Oct 2015 07:26:42 +0000 (UTC) Received: (qmail 19119 invoked by uid 500); 6 Oct 2015 07:26:29 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 19077 invoked by uid 500); 6 Oct 2015 07:26:29 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 19066 invoked by uid 99); 6 Oct 2015 07:26:29 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2015 07:26:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0C4DFC0470 for ; Tue, 6 Oct 2015 07:26:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.979 X-Spam-Level: ** X-Spam-Status: No, score=2.979 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id CQcncHyQ_7ai for ; Tue, 6 Oct 2015 07:26:28 +0000 (UTC) Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com [209.85.220.178]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id EF08920F20 for ; Tue, 6 Oct 2015 07:26:27 +0000 (UTC) Received: by qkbi190 with SMTP id i190so61201688qkb.1 for ; Tue, 06 Oct 2015 00:26:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=FpMuOKEsYpOzKo7MnGwo+EpAXGCgNw7/WjUPr1QmXf8=; b=aDKaJq/FmEnA0MUF98DxN4TDNp6rQHo6caPsBbZhQlYn1P4r5cvepKwcNtJ+XgXGv3 rLLZPPrE2eYgWcQkXVzw5vStmi/EnKnX5jaBvo7PhwhnLpj2qMux2Ru8Pb3ACYL7/PQW gNkBFvnMjdj3hSIAVeggGL33MRSz/YETCRyMm4c9vTyxeRtEPjtRCIKNmOASGWfPXigI U81SJQtmc5vsPPdNSVmBffwWohkqTXoMtnlqdQluekKHy9UdreHnTRJag1hAmfDdz/Zc Wq4d9g4SG5MzeWN7eDB1mwjlRz1HLy/xMUNLSvpPv2X41cOARsMl4XnfA4VplXzRBWiv xwhg== X-Gm-Message-State: ALoCoQlc4seilel+r4WKMggE53l5UFdyRl4IyDs/mtWKRTUeTpx4OyVM0bxHUKnKx0OS3DWmlYcS MIME-Version: 1.0 X-Received: by 10.140.100.136 with SMTP id s8mr44586710qge.47.1444116387131; Tue, 06 Oct 2015 00:26:27 -0700 (PDT) Received: by 10.140.20.167 with HTTP; Tue, 6 Oct 2015 00:26:27 -0700 (PDT) Date: Tue, 6 Oct 2015 10:26:27 +0300 Message-ID: Subject: Why portable marshaller handle Date and Timestamp in the same way? From: Vladimir Ozerov To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary=001a11c16e2e450dd205216a8cfe --001a11c16e2e450dd205216a8cfe Content-Type: text/plain; charset=UTF-8 Igniters, For some reason we "merged" Date and Timestamp types in portable marshaller. They are both written in the same format with the same type ID. And how date is interpreted on read side - as Date or as Timestamp - depends on configuration flag "use timestamp". Is there are reason why we do this? Transparent conversion from Timestamp to Date is invalid use case because it leads to data loss. Looks like we can separate these types from each other and remove this strange configuration parameter. Thoughts? Vladimir. --001a11c16e2e450dd205216a8cfe--