You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Kirk Lund <kl...@apache.org> on 2018/02/03 00:38:12 UTC
MigrationClient and MigrationServer
I just ran across two classes in org.apache.geode.internal package:
* MigrationClient
* MigrationServer
They have the javadoc @since GemFire 6.0.1 so I suspect these are no longer
useful or relevant. Can I delete these classes?
Thanks,
Kirk
Re: MigrationClient and MigrationServer
Posted by Michael Stolz <ms...@pivotal.io>.
Yeah we made a change to our diskstore format right around 6.0 that caused
customers to have to migrate all their persistent stores.
I don't think we have any plans to attempt any migrations from pre-6.0 any
more ;)
+1 for deleting these
--
Mike Stolz
Principal Engineer, GemFire Product Lead
Mobile: +1-631-835-4771
Download the new GemFire book here.
<https://content.pivotal.io/ebooks/scaling-data-services-with-pivotal-gemfire>
On Mon, Feb 5, 2018 at 1:08 PM, Anilkumar Gingade <ag...@pivotal.io>
wrote:
> Its used for data migration from one version to another...Don't see any
> mention of this in docs or any tools built around it.
>
> +1 for removal.
>
> -Anil.
>
>
> On Fri, Feb 2, 2018 at 4:38 PM, Kirk Lund <kl...@apache.org> wrote:
>
> > I just ran across two classes in org.apache.geode.internal package:
> > * MigrationClient
> > * MigrationServer
> >
> > They have the javadoc @since GemFire 6.0.1 so I suspect these are no
> longer
> > useful or relevant. Can I delete these classes?
> >
> > Thanks,
> > Kirk
> >
>
Re: MigrationClient and MigrationServer
Posted by Bruce Schuchardt <bs...@pivotal.io>.
+1
On 2/5/18 10:08 AM, Anilkumar Gingade wrote:
> Its used for data migration from one version to another...Don't see any
> mention of this in docs or any tools built around it.
>
> +1 for removal.
>
> -Anil.
>
>
> On Fri, Feb 2, 2018 at 4:38 PM, Kirk Lund <kl...@apache.org> wrote:
>
>> I just ran across two classes in org.apache.geode.internal package:
>> * MigrationClient
>> * MigrationServer
>>
>> They have the javadoc @since GemFire 6.0.1 so I suspect these are no longer
>> useful or relevant. Can I delete these classes?
>>
>> Thanks,
>> Kirk
>>
Re: MigrationClient and MigrationServer
Posted by Udo Kohlmeyer <uk...@pivotal.io>.
+1 to remove. UNLESS we want to start a migration module, which could
contain all the scripts or classes we require to do some migration on/off
line...
--Udo
On Mon, Feb 5, 2018 at 10:08 AM, Anilkumar Gingade <ag...@pivotal.io>
wrote:
> Its used for data migration from one version to another...Don't see any
> mention of this in docs or any tools built around it.
>
> +1 for removal.
>
> -Anil.
>
>
> On Fri, Feb 2, 2018 at 4:38 PM, Kirk Lund <kl...@apache.org> wrote:
>
> > I just ran across two classes in org.apache.geode.internal package:
> > * MigrationClient
> > * MigrationServer
> >
> > They have the javadoc @since GemFire 6.0.1 so I suspect these are no
> longer
> > useful or relevant. Can I delete these classes?
> >
> > Thanks,
> > Kirk
> >
>
Re: MigrationClient and MigrationServer
Posted by Anilkumar Gingade <ag...@pivotal.io>.
Its used for data migration from one version to another...Don't see any
mention of this in docs or any tools built around it.
+1 for removal.
-Anil.
On Fri, Feb 2, 2018 at 4:38 PM, Kirk Lund <kl...@apache.org> wrote:
> I just ran across two classes in org.apache.geode.internal package:
> * MigrationClient
> * MigrationServer
>
> They have the javadoc @since GemFire 6.0.1 so I suspect these are no longer
> useful or relevant. Can I delete these classes?
>
> Thanks,
> Kirk
>