[MTCGA]: new failures in builds [6437143] needs to be handled

[ignitetcbot]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 *Test with high flaky rate in master WebSessionV1SelfTest.testRestarts 
https://ci2.ignite.apache.org/test/-1286479574239436447?currentProjectId=IgniteTests24Java8=%3Cdefault%3E
 No changes in the build

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 02:53:21 19-05-2022 

Re: [DISCUSSION] Add additional 3rd party libraries to Ignite 3 Code style and practices

[Eduard Rakhmankulov]

Hi, Igniters!

I am really glad about the 140 symbol column limit.

But aside from possible vulnerabilities mentioned above I have other
concerns, which may affect some future users.

Micronaut is a rather popular framework. Are we planning some OSGI support
(or custom classloader magic) so users which have been already using
micronaut don't need to be bound to the version transitively inherited by
ignite dependencies?

On Thu, 19 May 2022 at 00:32, Andrey Gura  wrote:

> I personally don't support any additional 3rd party dependencies as
> well as I don't fully understand the value of autogenerated specs for
> REST endpoints. In my opinion we have another option: writing spec
> manually. This option doesn't require any of proposed dependencies and
> allow to avoid possible vulnerabilities. Of course at the cost of
> manual actions.
>
> I understand that my statement is arguable. So I'll just wait for
> opinions of other community members.
>
> On Mon, May 16, 2022 at 7:45 PM Aleksandr Pakhomov 
> wrote:
> >
> >
> > Hello, Igniters.
> >
> > I would like to start a discussion about Java Code Style Guide [1]
> changes that are going to be a part of IEP-87 [2] implementation. The set
> of libraries and frameworks that are going to be allowed to be used in
> production:
> > - Micronaut for REST Server [3]
> > - Swagger for Open API annotations [4]
> > - Micronaut serde for REST serialization [5]
> >
> > Any objections? Also, comments on IEP-87 are welcomed.
> > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide#JavaCodeStyleGuide-2Using3rdpartylibraries
> <
> https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide#JavaCodeStyleGuide-2Using3rdpartylibraries
> >
> > [2]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-87%3A+Open+API+support+for+REST#IEP87:OpenAPIsupportforREST-Additionaldependencies
> <
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-87%3A+Open+API+support+for+REST#IEP87:OpenAPIsupportforREST-Additionaldependencies
> >
> > [3] https://micronaut.io/docs /
> > [4] https://swagger.io 
> > [5]
> https://micronaut-projects.github.io/micronaut-serialization/snapshot/guide
> <
> https://micronaut-projects.github.io/micronaut-serialization/snapshot/guide
> >/
>

Re: [DISCUSSION] IEP-88: CLI Tool

[Andrey Gura]

> 1. Does “Ignite shell” sounds better?

I don't know. It could be Ignite REPL, IGnite Shell or something else.
Just an idea.

> But I did not get your point about scripting. What do you mean by saying “it 
> will just hang”?  What kind of error is going to be the cause of such 
> behaviour?

I can just have a mistake in my script, e.g. running ignite command
without any parameters. What will happen in such a case from the
script perspective? I think the script will wait for returning value
while the shell will wait for a user input. Due to a server-side
nature of the script it will hang forever because there is no user on
the server side.

On Thu, May 19, 2022 at 1:02 AM Aleksandr Pakhomov  wrote:
>
> Hi, Andrey
>
> Thanks for comments.
>
> 1. Does “Ignite shell” sounds better?
>
> 2. Yes, you are right. Most tools print help if they are executed without 
>   arguments. But I did not get your point about scripting. What do you mean 
> by saying “it will just hang”?  What kind of error is going to be the cause 
> of such behaviour?
>
> > On 18 May 2022, at 21:14, Andrey Gura  wrote:
> >
> > Hi,
> >
> > My two cents:
> >
> > 1. CLI Tool - looks like not the best name :) Shell?
> >
> > 2. The description says: "REPL mode is used by default and is
> > activated if the ignite command is executed without parameters."
> >
> > I think it is a bad idea. Firstly, it is usual CLI's behaviour to
> > print a help for a user. An exception if we would use a special CLI
> > for REPL. Shell? :)
> > Also such approach breaks my expectations related to a scripting. In
> > case of an error in a script it will just hang. So, a separate CLI
> > utility looks better than ignite CLI.
> >
> >
> > On Thu, May 12, 2022 at 11:43 PM Aleksandr Pakhomov  
> > wrote:
> >>
> >> Hello, Igniters.
> >>
> >> I’d like to start a discussion about Ignite 3 Command Line Tool [1]. The 
> >> main value is to develop a user-friendly command-line tool with advanced 
> >> completions and SQL REPL mode.
> >>
> >> The set of commands and parameters can be discussed. Questions and 
> >> comments are welcomed.
> >>
> >> [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-88%3A+CLI+Tool 
> >> 
>

Re: IEP-90 Ignite 3 Client Lifecycle

[Andrey Gura]

Igor,

Thanks for the proposal.

I understand that such a situation is almost impossible but "if
anything can go wrong, it will". Does the protocol take into account
that different connections on different client instances theoretically
could generate an already existing connection ID?

Also, do I understand correctly that a server has enough information
about client connections so it will be possible to observe a
connections list on the server? It would be useful for cluster
monitoring purposes.

On Tue, May 17, 2022 at 3:11 PM Igor Sapego  wrote:
>
> 1. I've tried to clarify IDs part;
> 2. Maybe you are right, though in this case we'd need to use authentication
> in ConnectionRestoreReq. Which sounds reasonable to me.
>
> Best Regards,
> Igor
>
>
> On Tue, May 17, 2022 at 10:47 AM Pavel Tupitsyn 
> wrote:
>
> > Igor,
> >
> > The proposal looks good to me. Very detailed!
> >
> > A couple comments:
> >
> > 1. There is a bit of a term mixup with "Connection ID", "Node ID", "Token"
> > - can you please review those?
> >
> > 2. > The Connection ID should be generated using a proper secure algorithm
> > (additional research is required here) to make sure an intruder can not
> > generate an existing Connection ID
> > Not sure about the reasoning here. I think randomUUID() should be enough:
> > - In the case of an unsecured cluster it does not matter, because anyone
> > can do anything.
> > - In the case of a secured cluster it does not matter, because
> > authentication/authorization keeps intruders out.
> >
> >
> > On Mon, May 16, 2022 at 11:07 PM Igor Sapego  wrote:
> >
> > > Hi, Igniters
> > >
> > > I've prepared an IEP for Ignite 3 Client Lifecycle [1]. The main idea is
> > to
> > > define client lifecycle as well as core algorithms and mechanisms used by
> > > clients. This proposal can be used as a reference for implementation of a
> > > new client for Ignite when dealing with such problems as:
> > >
> > >- Resolving of user-provided addresses;
> > >- Initial connection to a cluster;
> > >- Maintaining cluster connection;
> > >- Connection recovery;
> > >- Connection break handling.
> > >
> > > So take a look and let me know what you think guys.
> > >
> > > [1] -
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-90+Client+Lifecycle
> > >
> > > Best Regards,
> > > Igor
> > >
> >

Re: [DISCUSSION] IEP-88: CLI Tool

[Aleksandr Pakhomov]

Hi, Andrey

Thanks for comments.

1. Does “Ignite shell” sounds better? 

2. Yes, you are right. Most tools print help if they are executed without   
arguments. But I did not get your point about scripting. What do you mean by 
saying “it will just hang”?  What kind of error is going to be the cause of 
such behaviour?

> On 18 May 2022, at 21:14, Andrey Gura  wrote:
> 
> Hi,
> 
> My two cents:
> 
> 1. CLI Tool - looks like not the best name :) Shell?
> 
> 2. The description says: "REPL mode is used by default and is
> activated if the ignite command is executed without parameters."
> 
> I think it is a bad idea. Firstly, it is usual CLI's behaviour to
> print a help for a user. An exception if we would use a special CLI
> for REPL. Shell? :)
> Also such approach breaks my expectations related to a scripting. In
> case of an error in a script it will just hang. So, a separate CLI
> utility looks better than ignite CLI.
> 
> 
> On Thu, May 12, 2022 at 11:43 PM Aleksandr Pakhomov  wrote:
>> 
>> Hello, Igniters.
>> 
>> I’d like to start a discussion about Ignite 3 Command Line Tool [1]. The 
>> main value is to develop a user-friendly command-line tool with advanced 
>> completions and SQL REPL mode.
>> 
>> The set of commands and parameters can be discussed. Questions and comments 
>> are welcomed.
>> 
>> [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-88%3A+CLI+Tool 
>> 

Re: [DISCUSSION] Add additional 3rd party libraries to Ignite 3 Code style and practices

[Andrey Gura]

I personally don't support any additional 3rd party dependencies as
well as I don't fully understand the value of autogenerated specs for
REST endpoints. In my opinion we have another option: writing spec
manually. This option doesn't require any of proposed dependencies and
allow to avoid possible vulnerabilities. Of course at the cost of
manual actions.

I understand that my statement is arguable. So I'll just wait for
opinions of other community members.

On Mon, May 16, 2022 at 7:45 PM Aleksandr Pakhomov  wrote:
>
>
> Hello, Igniters.
>
> I would like to start a discussion about Java Code Style Guide [1] changes 
> that are going to be a part of IEP-87 [2] implementation. The set of 
> libraries and frameworks that are going to be allowed to be used in 
> production:
> - Micronaut for REST Server [3]
> - Swagger for Open API annotations [4]
> - Micronaut serde for REST serialization [5]
>
> Any objections? Also, comments on IEP-87 are welcomed.
> [1] 
> https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide#JavaCodeStyleGuide-2Using3rdpartylibraries
>  
> 
> [2] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-87%3A+Open+API+support+for+REST#IEP87:OpenAPIsupportforREST-Additionaldependencies
>  
> 
> [3] https://micronaut.io/docs /
> [4] https://swagger.io 
> [5] 
> https://micronaut-projects.github.io/micronaut-serialization/snapshot/guide 
> /

[MTCGA]: new failures in builds [6441382] needs to be handled

[ignitetcbot]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New test failure in master 
CacheAffinityCallSelfTest.testAffinityCallRestartNode 
https://ci2.ignite.apache.org/test/-7743809407709788864?currentProjectId=IgniteTests24Java8=%3Cdefault%3E
 Changes may lead to failure were done by 
 - vladimir steshin  
https://ci2.ignite.apache.org/viewModification.html?modId=953807

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 21:23:21 18-05-2022 

Re: [DISCUSSION] IEP-88: CLI Tool

[Andrey Gura]

Hi,

My two cents:

1. CLI Tool - looks like not the best name :) Shell?

2. The description says: "REPL mode is used by default and is
activated if the ignite command is executed without parameters."

I think it is a bad idea. Firstly, it is usual CLI's behaviour to
print a help for a user. An exception if we would use a special CLI
for REPL. Shell? :)
Also such approach breaks my expectations related to a scripting. In
case of an error in a script it will just hang. So, a separate CLI
utility looks better than ignite CLI.


On Thu, May 12, 2022 at 11:43 PM Aleksandr Pakhomov  wrote:
>
> Hello, Igniters.
>
> I’d like to start a discussion about Ignite 3 Command Line Tool [1]. The main 
> value is to develop a user-friendly command-line tool with advanced 
> completions and SQL REPL mode.
>
> The set of commands and parameters can be discussed. Questions and comments 
> are welcomed.
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-88%3A+CLI+Tool 
> 

[ANNOUNCE] Apache Ignite Extensions Released

[Maxim Muzafarov]

The Apache Ignite Community is pleased to announce the release of
the following Apache Ignite Extensions:
- Ignite AWS Extension 1.0.0
- Ignite Azure Extension 1.0.0
- Ignite GCE Extension 1.0.0
- Ignite Spring Data Extension 2.0.0
- Ignite Spring Session Extension 1.0.0
- Ignite Zookeeper Ip Finder Extension 1.0.0

Apache Ignite® is a Distributed Database For High-Performance
Computing With In-Memory Speed.
https://ignite.apache.org

Download the latest Ignite Extensions version from here:
https://ignite.apache.org/download.cgi

Please let us know if you encounter any problems:
https://ignite.apache.org/community/resources.html#ask


Regards,
Maxim Muzafarov on behalf of the Apache Ignite community.