Thanks, Pavel!
Anton, Alex, we're in agreement to merge the changes in Ignite 2.9. Please
go ahead removing the Hadoop/IGFS modules from both the master and 2.9
branches.
-
Denis
On Thu, Jul 23, 2020 at 8:14 AM Pavel Tupitsyn wrote:
> Denis,
>
> Thanks for the explanation, I don't have any
Denis,
Thanks for the explanation, I don't have any objections anymore.
On Wed, Jul 22, 2020 at 7:46 PM Denis Magda wrote:
> Hi,
>
> Send an email to this address: dev-unsubscr...@ignite.apache.org
>
> -
> Denis
>
>
> On Wed, Jul 22, 2020 at 9:28 AM C Ravikiran
> wrote:
>
> > Hi,
> >
> >
Hi,
Send an email to this address: dev-unsubscr...@ignite.apache.org
-
Denis
On Wed, Jul 22, 2020 at 9:28 AM C Ravikiran
wrote:
> Hi,
>
> Could you please help me to unsubscribe all these ignite mails.
>
> I have unsubscribed it, but still I am getting lot of emails
> Could you please help
The removal of these methods will not impact anybody during migration to
2.9. Unless you use the Hadoop Accelerator or IGFS in your application. In
the latter scenario, well, the integration has already been discontinued
and you need to clean your application code before moving forward to 2.9.
Hi,
Could you please help me to unsubscribe all these ignite mails.
I have unsubscribed it, but still I am getting lot of emails
Could you please help me..
On Wed, 22 Jul, 2020, 9:45 pm Anton Kalashnikov, wrote:
> Sorry, I was mistaken, we can not leave these methods because at least
>
Sorry, I was mistaken, we can not leave these methods because at least
FileSystemConfiguration and HadoopConfiguration require corresponded classes
that were deleted. So I think we should just remove it right now.
--
Best regards,
Anton Kalashnikov
22.07.2020, 18:56, "Anton Kalashnikov" :
>
Hi,
All of these methods are from IgniteConfiguration:
Hadoop configuration:
- HadoopConfiguration getHadoopConfiguration()
- IgniteConfiguration setHadoopConfiguration(HadoopConfiguration hadoopCfg)
IGFS (Ignite In-Memory File System) configurations:
- FileSystemConfiguration[]
Hi Alex,
It's been a year since we voted to discontinue this integration [1] and it
wasn't removed from the source code earlier only because of the internal
dependencies with the ML component. Now all the dependencies are gone and
Ignite 2.9 is the right version to finish the discontinuation
Guys,
Any updates here? Looks like we still don't have a consensus about release
version for this patch (already mention it in the release thread).
Currently, the ticket is still targeted to 2.9.
ср, 15 июл. 2020 г. в 00:40, Denis Magda :
> I don't think it's required to wait until Ignite 3.0
I don't think it's required to wait until Ignite 3.0 to make this happen.
If I'm not mistaken, we stopped releasing Hadoop binaries and sources a
long time ago (at least you can't longer find them on the downloads page).
Also, we removed all the mentioning from the documentation and website.
We are breaking backwards compatibility,
so this can be only done for Ignite 3.0, am I right?
On Thu, Jul 9, 2020 at 1:46 PM Anton Kalashnikov wrote:
> Hi everyone,
>
> The task of removal IGFS and Hadoop accelerator is ready to review.(
> https://issues.apache.org/jira/browse/IGNITE-11942)
>
Hi everyone,
The task of removal IGFS and Hadoop accelerator is ready to
review.(https://issues.apache.org/jira/browse/IGNITE-11942)
I've already asked some guys to take a look at it but if somebody familiar with
this part of code, feel free to take a look at the changes too(especially
scripts
Thank you so you much! Will wait:)
пн, 10 февр. 2020 г. в 15:13, Alexey Goncharuk :
> Got it, then no need to rush, let's wait for the TF-IGFS decoupling.
>
> пн, 10 февр. 2020 г. в 13:15, Alexey Zinoviev :
>
> > Tensorflow integration uses IGFS, if you have any idea how to store files
> > in
Got it, then no need to rush, let's wait for the TF-IGFS decoupling.
пн, 10 февр. 2020 г. в 13:15, Alexey Zinoviev :
> Tensorflow integration uses IGFS, if you have any idea how to store files
> in memory by another way, please suggest something.
> I hope to decouple Ignite-TF integration to the
Tensorflow integration uses IGFS, if you have any idea how to store files
in memory by another way, please suggest something.
I hope to decouple Ignite-TF integration to the separate repository before
release 2.9 with its own file system over Ignite Caches
пн, 10 февр. 2020 г. в 12:49, Ivan
Is not it blocked by
https://issues.apache.org/jira/browse/IGNITE-10292 as stated in JIRA?
@Alex Zinoviev could you please shed some light on this?
Best regards,
Ivan Pavlukhin
пн, 10 февр. 2020 г. в 12:46, Anton Kalashnikov :
>
> I found the correct ticket for such activity -
>
I found the correct ticket for such activity -
https://issues.apache.org/jira/browse/IGNITE-11942
--
Best regards,
Anton Kalashnikov
10.02.2020, 12:16, "Anton Kalashnikov" :
> Hello.
>
> I created a ticket for this activity -
> https://issues.apache.org/jira/browse/IGNITE-12647. And if we
Hello.
I created a ticket for this activity -
https://issues.apache.org/jira/browse/IGNITE-12647. And if we are still in
consensus I'll do it at the nearest time(I've already had the prepared code).
--
Best regards,
Anton Kalashnikov
10.02.2020, 12:07, "Alexey Goncharuk" :
> Folks,
>
> I
Folks,
I think there is a consensus here, but we did not remove IGFS neither in
2.7 nor in 2.8, did we? Should we schedule a corresponding ticket for 2.9?
Dmitriy,
I like the first approach with applying Maxim's idea of creating a branch
> named -igfs-Hadoop (not release, but current master state).
+1 for this approach. Any other opinions before we finalize this discussion?
-
Denis
On Tue, Jun 18, 2019 at 11:28 AM Dmitriy Pavlov wrote:
> Hi
Hi Denis,
I like the first approach with applying Maxim's idea of creating a branch
named -igfs-Hadoop (not release, but current master state).
2nd) 3rd party repo can be Apache repo just like ignite-release. But it's
true it is time-consuming to move code.
3rd) Attic is for projects, I hope no
Igniters,
Thanks a lot for sharing your opinion. As I see, there is a consensus that
IGFS and Hadoop Accelerator are to be discontinued and no longer supported
by the community.
As for the source code, if the community prefers moving the source code to
another repository rather than removing it,
Folks,
+1 to reduce the number of supported features.
Probably, the best solution will be removing IGFS from core module and
making it as an Ignite plugin (will require some efforts to do this).
I've also think we can move IGFS to the separate branch (from the
master one) if someone will decide
>
> +1 from me to reduce supported feature list.
> Guys, are we talking about Ignite 3.0?
Nikolay, I would discontinue IGFS before 3.0. Let's do this in the next
release? As for other features and integrations, 3.0 should be considered
as a version.
> +1 from me provided that we move sources
Hi Igniters,
+1 from me provided that we move sources to some supplementary repository.
If someone later would like to maintain/fix this module, he/she should be
able to access sources with current state of the master.
Sincerely,
Dmitriy Pavlov
пн, 17 июн. 2019 г. в 18:25, Igor Sapego :
> +1
+1 from me. Hadoop Accelerator seems like an outdated solution,
and I believe IGFS was only added to support Hadoop Accelerator.
Best Regards,
Igor
On Mon, Jun 17, 2019 at 12:00 PM Nikolay Izhikov
wrote:
> +1 from me to reduce supported feature list.
>
> Guys, are we talking about Ignite 3.0?
+1 from me to reduce supported feature list.
Guys, are we talking about Ignite 3.0?
В Пн, 17/06/2019 в 11:57 +0300, Alexey Goncharuk пишет:
> Denis,
>
> I fully support this idea.
>
> First, looking back, I do not think it was a good design in the first place
> to build IGFS on top of Ignite
Denis,
I fully support this idea.
First, looking back, I do not think it was a good design in the first place
to build IGFS on top of Ignite caches. Second, I have never seen a case
where IGFS provided significant performance boost. Usually it's either all
data already fits buffer cache, and
Denis,
I must say that aforementioned solutions for a Hadoop ecosystem appear
from time to time in questions on a user mailing list. So, it seems
that there is a practical need for such solutions.
But of course it does not mean that we should continue a support of
IGFS and Hadoop Accelerator. If
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
30 matches
Mail list logo
