You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Taras Ledkov <tl...@gridgain.com> on 2020/06/18 14:42:34 UTC
Introduce the ability for a user to manage binary types
[IGNITE-13154]
Hi,
I propose to introduce ability for a user to manage cluster binary types.
This functionality is useful when user needs to change schema without
cluster restart.
Motivation:
Rid users of manual operations in the folder 'binary_meta' and cluster
restart when they need change schema.
The proposed implementation contains restrictions (see [1]).
So I guess we add internal API and command for public command line tool
(control.sh)
with mode 'experimental' mode (the property
IGNITE_ENABLE_EXPERIMENTAL_COMMAND must be set).
Please take a look at the ticket / patch.
Any comments / suggestions?
[1]. https://issues.apache.org/jira/browse/IGNITE-13154
--
Taras Ledkov
Mail-To: tledkov@gridgain.com
Re: Introduce the ability for a user to manage binary types [IGNITE-13154]
Posted by Denis Magda <dm...@apache.org>.
Excellent. Let me know if my version of the message works for you. Shared
it in the pull-request.
-
Denis
On Fri, Jun 19, 2020 at 3:15 AM Taras Ledkov <tl...@gridgain.com> wrote:
> Hi,
>
> I change the error message [1].
> The suggestion at the message contains info about requirement to remove
> all data with old schema,
> then remove metadata by control.sh or manually by delete files and
> restart grid.
>
>
> [1].
>
> https://github.com/apache/ignite/pull/7936/files#diff-cb1981ab1a44f213b4cadafd80c611c5R1047
>
> On 19.06.2020 1:55, Denis Magda wrote:
> > Glad to see it coming! That was a pain in the neck.
> >
> > Could we also add a hint to the exception message when a type mismatch
> > happens? Basically, the exception should not only report details about
> the
> > mismatch but also suggest how to solve it. The text can mention these new
> > control.sh commands and advise to remove the old metadata.
> >
> > -
> > Denis
> >
> >
> > On Thu, Jun 18, 2020 at 7:42 AM Taras Ledkov <tl...@gridgain.com>
> wrote:
> >
> >> Hi,
> >>
> >> I propose to introduce ability for a user to manage cluster binary
> types.
> >> This functionality is useful when user needs to change schema without
> >> cluster restart.
> >>
> >> Motivation:
> >> Rid users of manual operations in the folder 'binary_meta' and cluster
> >> restart when they need change schema.
> >>
> >> The proposed implementation contains restrictions (see [1]).
> >> So I guess we add internal API and command for public command line tool
> >> (control.sh)
> >> with mode 'experimental' mode (the property
> >> IGNITE_ENABLE_EXPERIMENTAL_COMMAND must be set).
> >>
> >> Please take a look at the ticket / patch.
> >>
> >> Any comments / suggestions?
> >>
> >> [1]. https://issues.apache.org/jira/browse/IGNITE-13154
> >>
> >> --
> >> Taras Ledkov
> >> Mail-To: tledkov@gridgain.com
> >>
> >>
> --
> Taras Ledkov
> Mail-To: tledkov@gridgain.com
>
>
Re: Introduce the ability for a user to manage binary types
[IGNITE-13154]
Posted by Taras Ledkov <tl...@gridgain.com>.
Hi,
I change the error message [1].
The suggestion at the message contains info about requirement to remove
all data with old schema,
then remove metadata by control.sh or manually by delete files and
restart grid.
[1].
https://github.com/apache/ignite/pull/7936/files#diff-cb1981ab1a44f213b4cadafd80c611c5R1047
On 19.06.2020 1:55, Denis Magda wrote:
> Glad to see it coming! That was a pain in the neck.
>
> Could we also add a hint to the exception message when a type mismatch
> happens? Basically, the exception should not only report details about the
> mismatch but also suggest how to solve it. The text can mention these new
> control.sh commands and advise to remove the old metadata.
>
> -
> Denis
>
>
> On Thu, Jun 18, 2020 at 7:42 AM Taras Ledkov <tl...@gridgain.com> wrote:
>
>> Hi,
>>
>> I propose to introduce ability for a user to manage cluster binary types.
>> This functionality is useful when user needs to change schema without
>> cluster restart.
>>
>> Motivation:
>> Rid users of manual operations in the folder 'binary_meta' and cluster
>> restart when they need change schema.
>>
>> The proposed implementation contains restrictions (see [1]).
>> So I guess we add internal API and command for public command line tool
>> (control.sh)
>> with mode 'experimental' mode (the property
>> IGNITE_ENABLE_EXPERIMENTAL_COMMAND must be set).
>>
>> Please take a look at the ticket / patch.
>>
>> Any comments / suggestions?
>>
>> [1]. https://issues.apache.org/jira/browse/IGNITE-13154
>>
>> --
>> Taras Ledkov
>> Mail-To: tledkov@gridgain.com
>>
>>
--
Taras Ledkov
Mail-To: tledkov@gridgain.com
Re: Introduce the ability for a user to manage binary types [IGNITE-13154]
Posted by Denis Magda <dm...@apache.org>.
Glad to see it coming! That was a pain in the neck.
Could we also add a hint to the exception message when a type mismatch
happens? Basically, the exception should not only report details about the
mismatch but also suggest how to solve it. The text can mention these new
control.sh commands and advise to remove the old metadata.
-
Denis
On Thu, Jun 18, 2020 at 7:42 AM Taras Ledkov <tl...@gridgain.com> wrote:
> Hi,
>
> I propose to introduce ability for a user to manage cluster binary types.
> This functionality is useful when user needs to change schema without
> cluster restart.
>
> Motivation:
> Rid users of manual operations in the folder 'binary_meta' and cluster
> restart when they need change schema.
>
> The proposed implementation contains restrictions (see [1]).
> So I guess we add internal API and command for public command line tool
> (control.sh)
> with mode 'experimental' mode (the property
> IGNITE_ENABLE_EXPERIMENTAL_COMMAND must be set).
>
> Please take a look at the ticket / patch.
>
> Any comments / suggestions?
>
> [1]. https://issues.apache.org/jira/browse/IGNITE-13154
>
> --
> Taras Ledkov
> Mail-To: tledkov@gridgain.com
>
>