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 09DE5175CE for ; Tue, 5 May 2015 02:09:35 +0000 (UTC) Received: (qmail 10187 invoked by uid 500); 5 May 2015 02:09:34 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 10143 invoked by uid 500); 5 May 2015 02:09:34 -0000 Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.incubator.apache.org Delivered-To: mailing list dev@ignite.incubator.apache.org Received: (qmail 10131 invoked by uid 99); 5 May 2015 02:09:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 02:09:34 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of markojevtic@gmail.com does not designate 54.191.145.13 as permitted sender) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 02:09:27 +0000 Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id E284C206A4 for ; Tue, 5 May 2015 02:09:06 +0000 (UTC) Received: by wicmx19 with SMTP id mx19so89791519wic.1 for ; Mon, 04 May 2015 19:08:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=12ybwLRru7SCx188AQtek56RDQMn0wLQN7C2j1H/gpE=; b=naypj5IeId4b4adUriMra+5cWGaV767qVXjrlEP7jUwfuwguf32HuX9KI09VAkOI9C 2224VWtq/OIpOP8/B3/ZJQ5bKu2/bGurQ5ZJbHtBdx6gpJ7kOsDXyL7InObLIf766x/F rQKP8pUGQFM2quaeMR1SJDzwZgi2gNR0/VE12NSYlJFwmhoMRZPIbCv73NRg/+b7AgqB BpAR435ezxyYtidFNrK56x9dGlC+vsdjDpRZbPGfhAb9fpPoj1cWpZObsppIgEuY5okN 6QwCD/Qj3Q4seuhdnbhV3Cr8bXrZ1jZxCDzduHVrj8IT+Ho/cY4jGXK+BkscexfehT64 lt4w== X-Received: by 10.180.84.97 with SMTP id x1mr951466wiy.1.1430791700545; Mon, 04 May 2015 19:08:20 -0700 (PDT) Received: from [192.168.1.2] (178-221-56-119.dynamic.isp.telekom.rs. [178.221.56.119]) by mx.google.com with ESMTPSA id q4sm23154705wja.24.2015.05.04.19.08.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 May 2015 19:08:19 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Making Ignite In-Memory File System mountable From: Marko Jevtic In-Reply-To: Date: Tue, 5 May 2015 04:08:12 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: dev@ignite.incubator.apache.org X-Mailer: Apple Mail (2.2070.6) X-Virus-Checked: Checked by ClamAV on apache.org Sorry for dropping like this in the topic :) But I think it would be extremely useful if we Ignite would provide an = API to virtually expose structures in cache. Like computing on fly (on access) csv/excel files or pdf reports from = cache, besides the regular usage to access Ignite=E2=80=99s file system. Just an idea. > On May 5, 2015, at 3:58 AM, Dmitriy Setrakyan = wrote: >=20 > I have noticed a Jira filed to make IGFS mountable: > https://issues.apache.org/jira/browse/IGNITE-854 >=20 > The integration proposed is via Fuse framework which would allow us = mount > IGFS just like a regular Linux file system. >=20 > This seems like a pretty big undertaking. Even though it sounds pretty = cool > in theory, it would be interesting to find out form the community if > everyone else finds it useful and maybe suggest some potential use = cases > for it. >=20 > Also, seems like Fuse framework is not being actively developed. Last > release came out in July, 2013. How safe is it to use this framework? >=20 > D.