Remove IGFS map-reduce in 2.0

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Remove IGFS map-reduce in 2.0

Vladimir Ozerov
Folks,

In old pre-Hadoop-accelerator days we implemented map-reduce over native
IGFS API. See IgniteFileSystem.execute() methods. Later we recognized that
users prefer to work with Hadoop API, so we implemented Hadoop Accelerator
module.

I think it is time to remove IgniteFileSystem.execute() from API as no one
need it. Any objections?

Vladimir.
Reply | Threaded
Open this post in threaded view
|

Re: Remove IGFS map-reduce in 2.0

Sergi
Do we have any problems with it? I think if we have some functionality that
require no or little maintenance, then no reason to drop it.

Sergi

2017-04-19 12:28 GMT+03:00 Vladimir Ozerov <[hidden email]>:

> Folks,
>
> In old pre-Hadoop-accelerator days we implemented map-reduce over native
> IGFS API. See IgniteFileSystem.execute() methods. Later we recognized that
> users prefer to work with Hadoop API, so we implemented Hadoop Accelerator
> module.
>
> I think it is time to remove IgniteFileSystem.execute() from API as no one
> need it. Any objections?
>
> Vladimir.
>
Reply | Threaded
Open this post in threaded view
|

Re: Remove IGFS map-reduce in 2.0

Vladimir Ozerov
Nobody ever used, we never mentioned it in docs, and finally we developed
the whole Hadoop Accelerator as a replacement for it. On the one hand it
doesn't require any maintenance efforts, on the other hand this is dead and
deprecated API which was never used in practice.

This is why I propose to remove it. We can always return it back if needed,
thanks to Git history.

On Wed, Apr 19, 2017 at 12:40 PM, Sergi Vladykin <[hidden email]>
wrote:

> Do we have any problems with it? I think if we have some functionality that
> require no or little maintenance, then no reason to drop it.
>
> Sergi
>
> 2017-04-19 12:28 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
> > Folks,
> >
> > In old pre-Hadoop-accelerator days we implemented map-reduce over native
> > IGFS API. See IgniteFileSystem.execute() methods. Later we recognized
> that
> > users prefer to work with Hadoop API, so we implemented Hadoop
> Accelerator
> > module.
> >
> > I think it is time to remove IgniteFileSystem.execute() from API as no
> one
> > need it. Any objections?
> >
> > Vladimir.
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Remove IGFS map-reduce in 2.0

dsetrakyan
Vladimir, I am against removing any public APIs in general. Why not
deprecate it, especially if it does not have any maintenance overhead? We
should clear explain the new alternative to this API in Javadoc.

On Wed, Apr 19, 2017 at 2:47 AM, Vladimir Ozerov <[hidden email]>
wrote:

> Nobody ever used, we never mentioned it in docs, and finally we developed
> the whole Hadoop Accelerator as a replacement for it. On the one hand it
> doesn't require any maintenance efforts, on the other hand this is dead and
> deprecated API which was never used in practice.
>
> This is why I propose to remove it. We can always return it back if needed,
> thanks to Git history.
>
> On Wed, Apr 19, 2017 at 12:40 PM, Sergi Vladykin <[hidden email]
> >
> wrote:
>
> > Do we have any problems with it? I think if we have some functionality
> that
> > require no or little maintenance, then no reason to drop it.
> >
> > Sergi
> >
> > 2017-04-19 12:28 GMT+03:00 Vladimir Ozerov <[hidden email]>:
> >
> > > Folks,
> > >
> > > In old pre-Hadoop-accelerator days we implemented map-reduce over
> native
> > > IGFS API. See IgniteFileSystem.execute() methods. Later we recognized
> > that
> > > users prefer to work with Hadoop API, so we implemented Hadoop
> > Accelerator
> > > module.
> > >
> > > I think it is time to remove IgniteFileSystem.execute() from API as no
> > one
> > > need it. Any objections?
> > >
> > > Vladimir.
> > >
> >
>