Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1D0CA18454 for ; Fri, 4 Dec 2015 19:36:28 +0000 (UTC) Received: (qmail 79577 invoked by uid 500); 4 Dec 2015 19:36:27 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 79533 invoked by uid 500); 4 Dec 2015 19:36:27 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 79522 invoked by uid 99); 4 Dec 2015 19:36:27 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2015 19:36:27 +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 3DBADCCE33 for ; Fri, 4 Dec 2015 19:36:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.973 X-Spam-Level: X-Spam-Status: No, score=0.973 tagged_above=-999 required=6.31 tests=[SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ICbskQ96uY9d for ; Fri, 4 Dec 2015 19:36:12 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id BBB5220267 for ; Fri, 4 Dec 2015 19:36:12 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 036311B9560A for ; Fri, 4 Dec 2015 11:36:12 -0800 (PST) Date: Fri, 4 Dec 2015 11:26:47 -0800 (PST) From: Kobe To: user@ignite.apache.org Message-ID: <1449257207407-2142.post@n6.nabble.com> Subject: How is igfs:// URL resolved? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I am using IGFS to store large data files. The content is not fed to Hadoop (I have no Hadoop in my system now). IGFS runs in my tomcat container and exposes the IGFS files as URL to the web client. Without IGFS, I would put my content on local file system ad have Tomcat make it visible so: { Tomcat [ ( file ./data/foo ) ] } <=======> Browser (http://tomcat/myapp/data/foo) With IGFS, I assume I do this: { Tomcat [ IGFS myigfs ( file /data/foo ) ] } <=======> Browser (http://myserver/myapp/data/foo) That is, the client still access the content at URL /myapp/data/foo but somehow Tomcat must be able to map this URL to the IGFS URL igfs://myigfs@myserver:12345/ How do I map the incoming URL to the IGFS URL? thanx, /Kobe -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-is-igfs-URL-resolved-tp2142.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.