Re: [VOTE] Create separate Jira project and Confluence space for Ignite 3

[Dmitriy Pavlov]

-0 from my side.

That's fine if we have a separate project.
But since the mission and the statement of community is the same, I tend to
see 2&3 as the same project. The only difference is that 3 was started
from scratch (from the code point of view).

ср, 6 окт. 2021 г. в 00:23, Maxim Muzafarov :

> - 0 from me.
>
> This is OK if the projects are different, but not OK if they are
> sharing the same version history.
>
> On Tue, 5 Oct 2021 at 13:39, Andrey Mashenkov
>  wrote:
> >
> > +1
> >
> > вт, 5 окт. 2021 г., 13:33 Юрий :
> >
> > > +1
> > >
> > > вт, 5 окт. 2021 г. в 02:52, Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com>:
> > >
> > > > Hello Community,
> > > >
> > > > As discussed in [1], I would like to propose the creation of a
> separate
> > > > Jira project and Confluence space for Ignite 3.
> > > >
> > > > Ignite 2 and Ignite 3 are developed in parallel in separate repos,
> so we
> > > > need a clear separation in other tools as well - this will help to
> > > > streamline the development process. Please refer to the discussion
> for
> > > more
> > > > details.
> > > >
> > > > [1]
> > > >
> > > >
> > >
> https://lists.apache.org/thread.html/rdcad3fc64b9f3a848c93089baae2bee1124a97869a94f4a04dd80fdf%40%3Cdev.ignite.apache.org%3E
> > > >
> > > > Voting options:
> > > >
> > > >- +1 - Agree with the suggestion
> > > >- 0 - Don't care much about the suggestion
> > > >- -1 - Disagree with the suggestion
> > > >
> > > > This is a majority vote.
> > > >
> > > > Voting ends in 72 hours, at 5pm PDT on October 7:
> > > >
> > > >
> > >
> https://www.timeanddate.com/counters/fullscreen.html?mode=a&iso=20211007T17&year=2021&month=10&day=7&hour=17&min=0&sec=0&p0=224
> > > >
> > > > -Val
> > > >
> > >
> > >
> > > --
> > > Живи с улыбкой! :D
> > >
>

API Proposal: Declare IgniteClient::close that throws no exceptions (IGNITE-15688)

[Stanislav Lukyanov]

Hi Igniters,

I found the following usability issue with java thin client API.

Whenever you do `try (IgniteClient client = Ignition.startClient(cfg))`, you're 
forced to declare `catch (Exception e)`.

This is because IgniteClient interface currently doesn't override close() from 
AutoClosable. Because of that, it inherits `close() throws Exception`.
 
In fact, this shouldn't be required. `TcpIgniteClient implements IgniteClient` 
currently throws Exception but it doesn't need to - its code doesn't throw any 
checked exceptions.
 
Proposal:
• Add `@Overrides public void close()` with no `throws` to IgniteClient.
• Remove `throws Exception` from `TcpIgniteClient::close`
Note: this change is fully backwards-compatible. It is legal to narrow the 
scope of `throws` in a new version of a method.

I plan to do this in https://issues.apache.org/jira/browse/IGNITE-15688.

Any objections?

Thanks,
Stan

Re: API Proposal: Declare IgniteClient::close that throws no exceptions (IGNITE-15688)

[Igor Sapego]

Sounds good, no objections from my side.

Best Regards,
Igor


On Wed, Oct 6, 2021 at 11:46 AM Stanislav Lukyanov 
wrote:

> Hi Igniters,
>
> I found the following usability issue with java thin client API.
>
> Whenever you do `try (IgniteClient client = Ignition.startClient(cfg))`,
> you're forced to declare `catch (Exception e)`.
>
> This is because IgniteClient interface currently doesn't override close()
> from AutoClosable. Because of that, it inherits `close() throws Exception`.
>
> In fact, this shouldn't be required. `TcpIgniteClient implements
> IgniteClient` currently throws Exception but it doesn't need to - its code
> doesn't throw any checked exceptions.
>
> Proposal:
> • Add `@Overrides public void close()` with no `throws` to
> IgniteClient.
> • Remove `throws Exception` from `TcpIgniteClient::close`
> Note: this change is fully backwards-compatible. It is legal to narrow the
> scope of `throws` in a new version of a method.
>
> I plan to do this in https://issues.apache.org/jira/browse/IGNITE-15688.
>
> Any objections?
>
> Thanks,
> Stan

Re: API Proposal: Declare IgniteClient::close that throws no exceptions (IGNITE-15688)

[Stanislav Lukyanov]

Patch, PR and visa are in the ticket.

Igor, please review and merge when you're ready.

Thanks,
Stan

> On 6 Oct 2021, at 12:54, Igor Sapego  wrote:
> 
> Sounds good, no objections from my side.
> 
> Best Regards,
> Igor
> 
> 
> On Wed, Oct 6, 2021 at 11:46 AM Stanislav Lukyanov 
> wrote:
> 
>> Hi Igniters,
>> 
>> I found the following usability issue with java thin client API.
>> 
>> Whenever you do `try (IgniteClient client = Ignition.startClient(cfg))`,
>> you're forced to declare `catch (Exception e)`.
>> 
>> This is because IgniteClient interface currently doesn't override close()
>> from AutoClosable. Because of that, it inherits `close() throws Exception`.
>> 
>> In fact, this shouldn't be required. `TcpIgniteClient implements
>> IgniteClient` currently throws Exception but it doesn't need to - its code
>> doesn't throw any checked exceptions.
>> 
>> Proposal:
>>• Add `@Overrides public void close()` with no `throws` to
>> IgniteClient.
>>• Remove `throws Exception` from `TcpIgniteClient::close`
>> Note: this change is fully backwards-compatible. It is legal to narrow the
>> scope of `throws` in a new version of a method.
>> 
>> I plan to do this in https://issues.apache.org/jira/browse/IGNITE-15688.
>> 
>> Any objections?
>> 
>> Thanks,
>> Stan

Re: [VOTE] Create separate Jira project and Confluence space for Ignite 3

[Denis Magda]

Val,

As we discussed earlier, I don't fully support this idea but if what you
propose is the only reasonable and efficient way to carry on with Ignite 3
and 2 development efforts, then I trust your word. But even if this vote
passes I still would encourage you to experiment with the alternative - a
mandatory "Architecture" field in JIRA that requires to pick between
"Ignite 2" and "Ignite 3". Talk to the ASF INFRA team, there still might be
the way to keep a single JIRA project and simplify the development efforts.

-
Denis


On Wed, Oct 6, 2021 at 3:03 AM Dmitriy Pavlov  wrote:

> -0 from my side.
>
> That's fine if we have a separate project.
> But since the mission and the statement of community is the same, I tend to
> see 2&3 as the same project. The only difference is that 3 was started
> from scratch (from the code point of view).
>
> ср, 6 окт. 2021 г. в 00:23, Maxim Muzafarov :
>
> > - 0 from me.
> >
> > This is OK if the projects are different, but not OK if they are
> > sharing the same version history.
> >
> > On Tue, 5 Oct 2021 at 13:39, Andrey Mashenkov
> >  wrote:
> > >
> > > +1
> > >
> > > вт, 5 окт. 2021 г., 13:33 Юрий :
> > >
> > > > +1
> > > >
> > > > вт, 5 окт. 2021 г. в 02:52, Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com>:
> > > >
> > > > > Hello Community,
> > > > >
> > > > > As discussed in [1], I would like to propose the creation of a
> > separate
> > > > > Jira project and Confluence space for Ignite 3.
> > > > >
> > > > > Ignite 2 and Ignite 3 are developed in parallel in separate repos,
> > so we
> > > > > need a clear separation in other tools as well - this will help to
> > > > > streamline the development process. Please refer to the discussion
> > for
> > > > more
> > > > > details.
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> >
> https://lists.apache.org/thread.html/rdcad3fc64b9f3a848c93089baae2bee1124a97869a94f4a04dd80fdf%40%3Cdev.ignite.apache.org%3E
> > > > >
> > > > > Voting options:
> > > > >
> > > > >- +1 - Agree with the suggestion
> > > > >- 0 - Don't care much about the suggestion
> > > > >- -1 - Disagree with the suggestion
> > > > >
> > > > > This is a majority vote.
> > > > >
> > > > > Voting ends in 72 hours, at 5pm PDT on October 7:
> > > > >
> > > > >
> > > >
> >
> https://www.timeanddate.com/counters/fullscreen.html?mode=a&iso=20211007T17&year=2021&month=10&day=7&hour=17&min=0&sec=0&p0=224
> > > > >
> > > > > -Val
> > > > >
> > > >
> > > >
> > > > --
> > > > Живи с улыбкой! :D
> > > >
> >
>

Re: [VOTE] Create separate Jira project and Confluence space for Ignite 3

[Pavel Tupitsyn]

-1

We have already started using the existing JIRA and Confluence.
There are lots of tickets, IEPs, and commits interlinked with each other.
Introducing a new JIRA and Confluence will cause a huge mess.

On Wed, Oct 6, 2021 at 7:57 PM Denis Magda  wrote:

> Val,
>
> As we discussed earlier, I don't fully support this idea but if what you
> propose is the only reasonable and efficient way to carry on with Ignite 3
> and 2 development efforts, then I trust your word. But even if this vote
> passes I still would encourage you to experiment with the alternative - a
> mandatory "Architecture" field in JIRA that requires to pick between
> "Ignite 2" and "Ignite 3". Talk to the ASF INFRA team, there still might be
> the way to keep a single JIRA project and simplify the development efforts.
>
> -
> Denis
>
>
> On Wed, Oct 6, 2021 at 3:03 AM Dmitriy Pavlov  wrote:
>
> > -0 from my side.
> >
> > That's fine if we have a separate project.
> > But since the mission and the statement of community is the same, I tend
> to
> > see 2&3 as the same project. The only difference is that 3 was started
> > from scratch (from the code point of view).
> >
> > ср, 6 окт. 2021 г. в 00:23, Maxim Muzafarov :
> >
> > > - 0 from me.
> > >
> > > This is OK if the projects are different, but not OK if they are
> > > sharing the same version history.
> > >
> > > On Tue, 5 Oct 2021 at 13:39, Andrey Mashenkov
> > >  wrote:
> > > >
> > > > +1
> > > >
> > > > вт, 5 окт. 2021 г., 13:33 Юрий :
> > > >
> > > > > +1
> > > > >
> > > > > вт, 5 окт. 2021 г. в 02:52, Valentin Kulichenko <
> > > > > valentin.kuliche...@gmail.com>:
> > > > >
> > > > > > Hello Community,
> > > > > >
> > > > > > As discussed in [1], I would like to propose the creation of a
> > > separate
> > > > > > Jira project and Confluence space for Ignite 3.
> > > > > >
> > > > > > Ignite 2 and Ignite 3 are developed in parallel in separate
> repos,
> > > so we
> > > > > > need a clear separation in other tools as well - this will help
> to
> > > > > > streamline the development process. Please refer to the
> discussion
> > > for
> > > > > more
> > > > > > details.
> > > > > >
> > > > > > [1]
> > > > > >
> > > > > >
> > > > >
> > >
> >
> https://lists.apache.org/thread.html/rdcad3fc64b9f3a848c93089baae2bee1124a97869a94f4a04dd80fdf%40%3Cdev.ignite.apache.org%3E
> > > > > >
> > > > > > Voting options:
> > > > > >
> > > > > >- +1 - Agree with the suggestion
> > > > > >- 0 - Don't care much about the suggestion
> > > > > >- -1 - Disagree with the suggestion
> > > > > >
> > > > > > This is a majority vote.
> > > > > >
> > > > > > Voting ends in 72 hours, at 5pm PDT on October 7:
> > > > > >
> > > > > >
> > > > >
> > >
> >
> https://www.timeanddate.com/counters/fullscreen.html?mode=a&iso=20211007T17&year=2021&month=10&day=7&hour=17&min=0&sec=0&p0=224
> > > > > >
> > > > > > -Val
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Живи с улыбкой! :D
> > > > >
> > >
> >
>

Ignite Summit Cloud Edition Event Page/Community

[Kevin Corbett]

Hello Igniters!


Ignite Summit Cloud Edition is coming up pretty soon and I thought it would be 
great to help setup an event page on LinkedIn to spread awareness. When someone 
signs up, a notification is sent to the person’s network which helps encourage 
more people to sign up to attend as well. This event page is meant to be a 
community where we can share daily posts and news to those planning to attend.


It would be great if you guys could sign up and maybe even invite some relevant 
contacts from your LinkedIn networks if possible. If you think someone should 
attend, feel free to invite them! :)

I’m excited to see how much this group grows over the course of the next couple 
of weeks!


LinkedIn Event Page Link: 
https://www.linkedin.com/events/ignitesummit-cloudedition6851552481613250560/ 


Attending and inviting others is as simple as: 
- Click the above link and sign into your LinkedIn account
- Click the “Attend” button below the Ignite Summit profile picture
- Click the “Invite” button which has replaced the “Attend” button
- Select relevant contacts and then click “Invite” at the bottom right of this 
popup


Thank you!

---
Kevin