Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CF557200CF7 for ; Tue, 19 Sep 2017 13:16:48 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CDFCD1609DD; Tue, 19 Sep 2017 11:16:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1F16F1609DB for ; Tue, 19 Sep 2017 13:16:47 +0200 (CEST) Received: (qmail 90953 invoked by uid 500); 19 Sep 2017 11:16:47 -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 90938 invoked by uid 99); 19 Sep 2017 11:16:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Sep 2017 11:16:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6F4721A53B4 for ; Tue, 19 Sep 2017 11:16:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.479 X-Spam-Level: ** X-Spam-Status: No, score=2.479 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Y0TtpdXsDQjJ for ; Tue, 19 Sep 2017 11:16:45 +0000 (UTC) Received: from mail-ua0-f173.google.com (mail-ua0-f173.google.com [209.85.217.173]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 3C1DA5FDBC for ; Tue, 19 Sep 2017 11:16:45 +0000 (UTC) Received: by mail-ua0-f173.google.com with SMTP id t36so1957335uah.10 for ; Tue, 19 Sep 2017 04:16:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=MLDkFxydr+pZS+JCJxmccbjwt8+CPPP9o+KetkYOdUU=; b=SCuqeJI0eMJGbcU5XapmShvEgRetGKUdMTyRyA22pgOBSnOP1rAYl/fn3fAnH4Oq0O KOJrTrKsM5Mj9ztADDT7d1pD4BUVw6nFCdsk4aR8Z56z21mHVbRDpNuH7QmMp2zcCWjC gkJwEZkIID3Im9Fip4RdRL7OL8bvs7W8T4+BdsAuswsH8CXFUrel36OGN78S3BgXJOd4 iI/z05p7KxSIpwsQj6G60uv5gtmrm1v02JT2h+n7Grp99Jv9EA26shN4bu4c8OXFcett 0ydj3oVE9qqOaTM6bcSHF29JSOci7wPvMt9r5HfsXnP/7KmFtviklwiQu20VLKojvya7 kWvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=MLDkFxydr+pZS+JCJxmccbjwt8+CPPP9o+KetkYOdUU=; b=SOBBdXkaJY2OOhIZ8UGn4GlCXxXeK3Vq5ZzZ6eYwLW8I2vE9GzsZrxHPlWK034oGQR Bx2tefXxxLf3LfLj4imilITj8zP9J9QXLzmry7JPYClCHtAbDBl4NnWef2534ucsstDJ KwwawQtXG5l6ZQRerECuBwIPGxUBRCAZZwN6qnhbj9vcy1IMPLVkRaslIj5M0sfWMDo4 6ULxvfeUAZ7MNpAEfrsmQIvDGRUxmSdqV1KWMgDUPOjFcapzEBbMMTYkBiLKDF744nGo /+M/0zNt1HQpUqbgQ931u+o0/KwescBXewekKSCgic8V0srXaxWWxWz6tMb1mMnmeDro rxEg== X-Gm-Message-State: AHPjjUhKikUG10mmWxw2GlhotOXgAfJEHJIITw/ou3nHzz1SSQDMdNCa 6iwTu7jy6/N/uowQAiKj2dSkRIR2pIdWpJYu6ckVdw== X-Google-Smtp-Source: AOwi7QBagZSncWBzeUF/M5j8Q5/oHhg9u865y5XLseRmyp8noCixnqWQqUgNNrDKbKc1eySA8nuVHML8KENn9kbmLL8= X-Received: by 10.176.18.98 with SMTP id s34mr895658uac.166.1505819799569; Tue, 19 Sep 2017 04:16:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.89.193 with HTTP; Tue, 19 Sep 2017 04:16:39 -0700 (PDT) From: Vladimir Ozerov Date: Tue, 19 Sep 2017 14:16:39 +0300 Message-ID: Subject: Binary compatibility of persistent storage To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="f403043664a63fdfa6055988febb" archived-at: Tue, 19 Sep 2017 11:16:49 -0000 --f403043664a63fdfa6055988febb Content-Type: text/plain; charset="UTF-8" igniters, Ignite doesn't have compatibility for binary protocols between different versions, as this would make development harder and slower. On the other hand we maintain API compatibility what helps us move users to new versions faster. As native persistence is implemented, new challenge appeared - whether to maintain binary compatibility of stored data. Many approaches exist: 1) No compatibility at all - easy for us, nightmare for users (IMO) 2) No compatibility, but provide migration instruments 3) Maintain compatibility between N latest minor versions 4) Maintain compatibility between all versions within major release The more guarantees we offer, the harder them to maintain, the better UX. Let's think on what compatibility mode we can offer to our users if any. Any ideas? Vladimir. --f403043664a63fdfa6055988febb--