Alex,
I've separated all to-be-removed points from existing
> Ignite 3.0 wishlist [1] to a dedicated block and also added a few more
> things that look right to be dropped.
Could you please share a reference to the wishlist? It's not in your
original email nor anywhere else in the discussion.
Generally speaking, I would group to-be-removed capabilities by Components,
Integrations, and APIs. Here is how my list looks like:
1. Components - IGFS and In-Memory Hadoop Accelerator. Strongly suggest
we to not putting off this procedure until 3.0 but execute the decision in
the next Ignite release. Refer to this thread [1] for details.
2. Integrations (aka. modules or plugins):
- Remove completely OR move to Github cemetery and no longer support
for every Ignite releases: Twitter, ZeroMQ, RocketMQ, Storm,
Flume, Flink,
MQTT, Camel, Hibernate, JMS, OSGi, YARN, Mesos, AOP-Based Grid
<https://apacheignite.readme.io/docs/aop-based-grid-enabling>,
ignite-clients
module <https://github.com/apache/ignite/tree/master/modules/clients>
- Preserve and move to separate repositories (to be supported by the
community). The goal is to separate Ignite core from
modules/plugins: Spark
Integration, TensorFlow, Cassandra Integration (ING), SpringData,
SpringBoot, Spring Caching, Kafka Integration.
- Move to separate repositories: thin clients (at least non-Java ones)
3. APIs:
- Remove: Redis and Memcached protocols support, compute
checkpointing SPI, geospatial support
- Should we remove the following or invest our time in better
support? - full-text search, Ignite messaging
I would put all of the suggestions on the wiki or on that wishlist and
track everything there while the discussion continues.
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
-
Denis
On Mon, Jun 17, 2019 at 5:18 AM Alexey Goncharuk <agoncha...@apache.org>
wrote:
> Igniters,
>
> Even though we are still planning the Ignite 2.8 release, I would like to
> kick-off a discussion related to Ignite 3.0, because the efforts for AI 3.0
> will be significantly larger than for AI 2.8, better to start early.
>
> As a first step, I would like to discuss the list of things to be removed
> in Ignite 3.0 (partially this thread is inspired by Denis Magda's IGFS
> removal thread). I've separated all to-be-removed points from existing
> Ignite 3.0 wishlist [1] to a dedicated block and also added a few more
> things that look right to be dropped.
>
> Please share your thoughts, probably, there are more outdated things we
> need to add to the wishlist.
>
> As a side question: I think it makes sense to create tickets for such
> improvements, how do we track them. Will the 3.0 version suffice or should
> we add a separate label?
>
> --AG
>
