From dev-return-46246-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Jun 12 18:04:50 2019 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id F221218061A for ; Wed, 12 Jun 2019 20:04:49 +0200 (CEST) Received: (qmail 59400 invoked by uid 500); 12 Jun 2019 18:04:49 -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 59371 invoked by uid 99); 12 Jun 2019 18:04:49 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jun 2019 18:04:49 +0000 Received: from mail-it1-f180.google.com (mail-it1-f180.google.com [209.85.166.180]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 74B128B5D for ; Wed, 12 Jun 2019 18:04:45 +0000 (UTC) Received: by mail-it1-f180.google.com with SMTP id j204so12021913ite.4 for ; Wed, 12 Jun 2019 11:04:45 -0700 (PDT) X-Gm-Message-State: APjAAAXR6UNvjJgPSvecv0T0KuFAWojnjoPIJAt4wZiXjLwNdpNUpQ/u VuGSqjt92CCDZo1Jsd/cY4aPmxFERWW7dW7nNkIAfA== X-Google-Smtp-Source: APXvYqwdjXUOPv5in/znuahJsjk/qbb+kfOAwQBHcSQJnyBA+L9D/2kgwfus87tPcG0sLGfgTAbds9axeWS1zDaorMg= X-Received: by 2002:a02:c00f:: with SMTP id y15mr54970435jai.132.1560362685125; Wed, 12 Jun 2019 11:04:45 -0700 (PDT) MIME-Version: 1.0 From: Denis Magda Date: Wed, 12 Jun 2019 11:04:19 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: [DISCUSSION] Complete Discontinuation of IGFS and Hadoop Accelerator To: dev Content-Type: multipart/alternative; boundary="000000000000917958058b243f2b" --000000000000917958058b243f2b Content-Type: text/plain; charset="UTF-8" Igniters, I'd like us to move on and finish our conversation on the IGFS [1] and Hadoop Accelerator [2] support. To my knowledge, there is no single committer who maintains the integrations; they are no longer tested and, even more, the community stopped providing the binaries since Ignite 2.6.0 release (look for In-Memory Hadoop Accelerator table [3]). Why all of that happened? Because of a little value, something succeeds while something fails. Does it mean that Ignite cannot be used for Hadoop acceleration, in general? No, quite the opposite, it CAN be used, but a solution is different. Have Ignite with native persistence deployed close to your Hadoop cluster (replace GridGain with Ignite) [4]. So, I propose we remove IGFS and In-Memory Hadoop Accelerator from our master repository and rework existing public documentation showing how to achieve the acceleration with Ignite. Any supporters or objections? [1] https://apacheignite-fs.readme.io/docs/in-memory-file-system [2] https://apacheignite-fs.readme.io/docs/hadoop-accelerator [3] https://ignite.apache.org/download.cgi#binaries [4] https://docs.gridgain.com/docs/bdb-getting-started#section-gridgain-data-lake-accelerator - Denis --000000000000917958058b243f2b--