ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject [DISCUSSION] Complete Discontinuation of IGFS and Hadoop Accelerator
Date Wed, 12 Jun 2019 18:04:19 GMT
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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message