From dev-return-37389-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Aug 3 12:21:40 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5A233180647 for ; Fri, 3 Aug 2018 12:21:40 +0200 (CEST) Received: (qmail 4769 invoked by uid 500); 3 Aug 2018 10:21:39 -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 4754 invoked by uid 99); 3 Aug 2018 10:21:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Aug 2018 10:21:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 56533C5703 for ; Fri, 3 Aug 2018 10:21:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.889 X-Spam-Level: * X-Spam-Status: No, score=1.889 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id fW7q3VNfggdO for ; Fri, 3 Aug 2018 10:21:37 +0000 (UTC) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id CE2A75F11F for ; Fri, 3 Aug 2018 10:21:36 +0000 (UTC) Received: by mail-lf1-f52.google.com with SMTP id n96-v6so3707428lfi.1 for ; Fri, 03 Aug 2018 03:21:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=sH8bijtFtSTA2CmByH9QmrCStjX29VkKHUnp/EC6Aqs=; b=KK8N53aJrZLIreFTm31xSSD36Cgp6PWvS2rPEyRlw6A4vSRfMfu5chKvC2YzpiLu+y QRsxfiPVcdXuC+trhCwnchjvfWb2RkpONWUHtMQuLRJCKGjl/TS9v/Om47ClXad84m90 7b0kFJ8mxXXZIRaDM2zMlQYxjTgBQEyBQXpmeYf3xE/jjXfEul0sdl5bbY59bo8y48Ks 0il7b6dWoVfENzq9n8LYDvFP0+c9WIeRmqmFfEkgwbIDQaOMDnsguGddjxfxS9Wquxy4 B6UE4aoTzmQsh5pstklARaWa2pwbnO/WPnV/i4Um7w16sXC1vDyD3yeF5BPKH4BBs3hg BwgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=sH8bijtFtSTA2CmByH9QmrCStjX29VkKHUnp/EC6Aqs=; b=a8Gnm2i7CbKvPg50bygFx6R92NtbsLRXBciuNjb7p82wdd6duR+WhS5FttWUzeiATj QUp7OVLG3jnzfofGPefwBbc4UJkfduFys99AnK19wUuz5Tbb3Dy54ls09V2p3mPq/82v o5RcQW6u+3iCFzW+YSiW9fpaZ/FPRhRqPT2MPshIT9Vymq3zg1a5KmuC8lX+mkYTHj0S ckcxbDzeW79L7lIDdTmQYBVmnBTiTiBMWyZL1MyvJlh0OE61WMDHYplLfbPM39OibUJ8 Clqpe2PfVyYwDWPo/zn6SAbJmYVVp3RRLx7qUCYosuaF44ntXA1sg4AHaCGOkSVkw1c9 wVXQ== X-Gm-Message-State: AOUpUlEW+WfPxflUXOkIb74QdVatweH9yb7649dSHMAiQzKa0tXMuSsA OvpZh4XnAM+2gEhZrE4DlXE4CdzkcQ9/AmSXAKUzcg== X-Google-Smtp-Source: AAOMgpcuR5PP/XhciqoGQocEQbp47V9z3KAI6Z+c3PN7L7xXx9iyajgM8sZRJ2iYULY2rQD3got/UlPfRdYgiIbjYWQ= X-Received: by 2002:a19:b598:: with SMTP id g24-v6mr4408250lfk.129.1533291696166; Fri, 03 Aug 2018 03:21:36 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:8198:0:0:0:0:0 with HTTP; Fri, 3 Aug 2018 03:21:35 -0700 (PDT) In-Reply-To: References: From: Pavel Kovalenko Date: Fri, 3 Aug 2018 13:21:35 +0300 Message-ID: Subject: Re: Ignite as distributed file storage To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="000000000000e31b4b0572854ac9" --000000000000e31b4b0572854ac9 Content-Type: text/plain; charset="UTF-8" Dmitriy, I think we don't need a separate implementation of cache like BLOB cache. Instead of it, a user can mark value class or value class field with the special annotation "@BLOB". During cache put, marshaller will place a special placeholder on such fields, write byte[] array payload of a field to special internal blob storage and place the only reference to actual DataEntry in the page memory. During cache get, marshaller will place a special proxy instead of an actual class that can be downloaded and unmarshalled by demand from internal storage on the user side. Using such approach we will also solve eager/lazy problem, this will also give user possibility to adjust his own marshallers (like Jackson, Jaxb, etc.) to marshal/unmarshal his blob classes from/to byte[] arrays. No major changes in public API are required, it can be pluggable component. 2018-08-03 0:25 GMT+03:00 Dmitriy Setrakyan : > On Thu, Aug 2, 2018 at 1:08 AM, Pavel Kovalenko > wrote: > > > Dmitriy, > > > > I still don't understand why do you think that it will be file system? > > In all my previous messages I emphasized that this storage shouldn't be > > considered as a file system. It's just a large data storage, whose > entities > > can be easily accessed using key/link (internally, or externally using > > web/binary protocol interfaces). > > > > > Instead, if we must focus on large blobs, I would solve the problem of > > supporting large blobs in regular Ignite caches, as I suggested before. > > > > This is impossible. Our page memory can't handle efficiently it by > design. > > > > But our API does. What is stopping us from creating a cache as a BLOB cache > and using whatever storage we need? > --000000000000e31b4b0572854ac9--