Re: [jira] [Created] (IGNITE-13696) [ML] Tutorial examples fails

[Ivan Daschinsky]

I'm sorry, but this is so funny, can't stop laughing :)

ср, 11 нояб. 2020 г. в 23:19, Alexey Zinoviev :

> What errors did you found?
>
> ср, 11 нояб. 2020 г., 22:13 Stepan Pilschikov (Jira) :
>
> > Stepan Pilschikov created IGNITE-13696:
> > --
> >
> >  Summary: [ML] Tutorial examples fails
> >  Key: IGNITE-13696
> >  URL: https://issues.apache.org/jira/browse/IGNITE-13696
> >  Project: Ignite
> >   Issue Type: Bug
> >   Components: examples, ml
> > Affects Versions: 2.9
> > Reporter: Stepan Pilschikov
> >
> >
> > Trying to run Tutorial examples from repository or from binary release
> and
> > meet error results. Looks like a bug
> >
> > org.apache.ignite.examples.ml.tutorial.Step_1_Read_and_Learn (all other
> > tutorials have same issue)
> > {code}
> > >>> Trained model: if (x0 > 2.5000) then if (x1 > 2.5000) then if (x2 >
> > 0.5000) then if (x1 > 4.5000) then return 0. else if (x2 > 1.5000)
> then
> > return 0. else return 0. else return 0. else if (x2 > 0.5000)
> > then if (x2 > 3.5000) then if (x1 > 0.5000) then return 0. else
> return
> > 0. else if (x2 > 1.5000) then return 0. else return 1. else
> if
> > (x1 > 0.5000) then if (x1 > 1.5000) then return 0. else return 0.
> > else return 0. else if (x2 > 0.5000) then if (x1 > 0.5000) then if
> (x1
> > > 1.5000) then if (x1 > 2.5000) then return 1. else return 1.
> else
> > if (x2 > 3.5000) then return 0. else return 1. else if (x2 >
> > 1.5000) then if (x0 > 1.5000) then return 1. else return 1. else
> if
> > (x0 > 1.5000) then return 1. else return 1. else if (x0 > 1.5000)
> > then if (x1 > 2.5000) then return 1. else if (x1 > 1.5000) then
> return
> > 0. else return 0. else if (x1 > 0.5000) then if (x1 > 1.5000)
> then
> > return 1. else return 1. else return 1.
> >
> > >>> Accuracy 0.7117737003058104
> >
> > >>> Test Error 0.28822629969418956
> > >>> Tutorial step 1 (read and learn) example completed.
> > {code}
> >
> >
> >
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.4#803005)
> >
>


-- 
Sincerely yours, Ivan Daschinskiy

Ignite documentation: things to pay attention to

[Denis Magda]

Igniters,

It's a pleasure to see that many more of us started contributing to the
Ignite documentation once we migrated from readme.io. The new docs plus a
growing number of contributors willing to keep the docs accurate, complete,
and valuable for the users is a significant achievement for our community
and project!

So, what's next? To avoid the docs' quality to fall into decay, we need to
treat their quality as seriously as we treat the quality of the overall
Ignite implementation. Please follow two simple rules if you're improving
our pages:

   1. Always check your changes against an app/service that corrects typos
   and grammar issues before submitting a pull-request. I use Grammarly
    that has a free tier.
   2. Make sure your pull-request is reviewed by a contributor with
   technical writing experience (presently, that's just me, but two more
   experts are about to join the community). We prefer pre-commit reviews.

Also, don't be discouraged if X% of your text is revised! We, contributors
with technical writing experience, want your contributions and can't
document anything unless you share details. But more than that, we want our
users to have fewer hiccups and headaches while building Ignite apps with
the help of professionally written documentation. The latter should be our
common goal. I hope we are on the same page.

Happy to answer your questions and clarify any points.

-
Denis

Re: [jira] [Created] (IGNITE-13696) [ML] Tutorial examples fails

[Alexey Zinoviev]

What errors did you found?

ср, 11 нояб. 2020 г., 22:13 Stepan Pilschikov (Jira) :

> Stepan Pilschikov created IGNITE-13696:
> --
>
>  Summary: [ML] Tutorial examples fails
>  Key: IGNITE-13696
>  URL: https://issues.apache.org/jira/browse/IGNITE-13696
>  Project: Ignite
>   Issue Type: Bug
>   Components: examples, ml
> Affects Versions: 2.9
> Reporter: Stepan Pilschikov
>
>
> Trying to run Tutorial examples from repository or from binary release and
> meet error results. Looks like a bug
>
> org.apache.ignite.examples.ml.tutorial.Step_1_Read_and_Learn (all other
> tutorials have same issue)
> {code}
> >>> Trained model: if (x0 > 2.5000) then if (x1 > 2.5000) then if (x2 >
> 0.5000) then if (x1 > 4.5000) then return 0. else if (x2 > 1.5000) then
> return 0. else return 0. else return 0. else if (x2 > 0.5000)
> then if (x2 > 3.5000) then if (x1 > 0.5000) then return 0. else return
> 0. else if (x2 > 1.5000) then return 0. else return 1. else if
> (x1 > 0.5000) then if (x1 > 1.5000) then return 0. else return 0.
> else return 0. else if (x2 > 0.5000) then if (x1 > 0.5000) then if (x1
> > 1.5000) then if (x1 > 2.5000) then return 1. else return 1. else
> if (x2 > 3.5000) then return 0. else return 1. else if (x2 >
> 1.5000) then if (x0 > 1.5000) then return 1. else return 1. else if
> (x0 > 1.5000) then return 1. else return 1. else if (x0 > 1.5000)
> then if (x1 > 2.5000) then return 1. else if (x1 > 1.5000) then return
> 0. else return 0. else if (x1 > 0.5000) then if (x1 > 1.5000) then
> return 1. else return 1. else return 1.
>
> >>> Accuracy 0.7117737003058104
>
> >>> Test Error 0.28822629969418956
> >>> Tutorial step 1 (read and learn) example completed.
> {code}
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>

[jira] [Created] (IGNITE-13696) [ML] Tutorial examples fails

[Stepan Pilschikov (Jira)]

Stepan Pilschikov created IGNITE-13696:
--

 Summary: [ML] Tutorial examples fails
 Key: IGNITE-13696
 URL: https://issues.apache.org/jira/browse/IGNITE-13696
 Project: Ignite
  Issue Type: Bug
  Components: examples, ml
Affects Versions: 2.9
Reporter: Stepan Pilschikov


Trying to run Tutorial examples from repository or from binary release and meet 
error results. Looks like a bug

org.apache.ignite.examples.ml.tutorial.Step_1_Read_and_Learn (all other 
tutorials have same issue)
{code}
>>> Trained model: if (x0 > 2.5000) then if (x1 > 2.5000) then if (x2 > 0.5000) 
>>> then if (x1 > 4.5000) then return 0. else if (x2 > 1.5000) then return 
>>> 0. else return 0. else return 0. else if (x2 > 0.5000) then if 
>>> (x2 > 3.5000) then if (x1 > 0.5000) then return 0. else return 0. 
>>> else if (x2 > 1.5000) then return 0. else return 1. else if (x1 > 
>>> 0.5000) then if (x1 > 1.5000) then return 0. else return 0. else 
>>> return 0. else if (x2 > 0.5000) then if (x1 > 0.5000) then if (x1 > 
>>> 1.5000) then if (x1 > 2.5000) then return 1. else return 1. else if 
>>> (x2 > 3.5000) then return 0. else return 1. else if (x2 > 1.5000) 
>>> then if (x0 > 1.5000) then return 1. else return 1. else if (x0 > 
>>> 1.5000) then return 1. else return 1. else if (x0 > 1.5000) then if 
>>> (x1 > 2.5000) then return 1. else if (x1 > 1.5000) then return 0. 
>>> else return 0. else if (x1 > 0.5000) then if (x1 > 1.5000) then return 
>>> 1. else return 1. else return 1.

>>> Accuracy 0.7117737003058104

>>> Test Error 0.28822629969418956
>>> Tutorial step 1 (read and learn) example completed.
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[dpavlov . tasks]

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 Critical Failure in master JCache TCK 1.1 
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_JCacheTck11?branch=%3Cdefault%3E
 Changes may lead to failure were done by 
 - igor sapego  
https://ci.ignite.apache.org/viewModification.html?modId=909652

 - 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 20:52:45 11-11-2020 

[jira] [Created] (IGNITE-13695) Move javadoc of affection of several addresses on failure detection.

[Vladimir Steshin (Jira)]

Vladimir Steshin created IGNITE-13695:
-

 Summary: Move javadoc of affection of several addresses on failure 
detection.
 Key: IGNITE-13695
 URL: https://issues.apache.org/jira/browse/IGNITE-13695
 Project: Ignite
  Issue Type: Bug
Reporter: Vladimir Steshin
Assignee: Vladimir Steshin


Current javadoc of affection several node addresses of failure detection is 
located under `TcpDiscoverySpi.setIpFinder()`. Correct place is by 
`TcpDiscoverySpi.setLocalAddress()`.
Perhaps, the test might be slightly changed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13694) Check difference between SIGTERM, SIGKILL and Disconnect at Cellular switch

[Anton Vinogradov (Jira)]

Anton Vinogradov created IGNITE-13694:
-

 Summary: Check difference between SIGTERM, SIGKILL and Disconnect 
at Cellular switch
 Key: IGNITE-13694
 URL: https://issues.apache.org/jira/browse/IGNITE-13694
 Project: Ignite
  Issue Type: Improvement
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] Release Ignite streamer extensions

[Mikhail Petrov]

Alexey,

Did I understand you correctly?

For each new version of any extension, the minimum Ignite version and 
the minimum version of  will be explicitly specified 
in the release notes/documentation. It is also assumed that due to 
backward compatibility users can safely use this extension with any 
version of Ignite and  that is higher than the 
specified minimum versions. And if any version of Ignite or target> don't satisfy backward compatibility, new version of the 
corresponding extension must be released.


If so, should we in this case get rid of multiple existing 
ignite-spring-data-[2.0, 2.1, 2.2] modules and just successively release 
existing modules with separate versions?


On 11.11.2020 11:54, Nikolay Izhikov wrote:

+1 to make extensions as independent as possible.

Doubt if we can do it for each module.
We have, ignite-hibernate_4.2, ignite-hibernate_5.1 modules that attached to 
specific hibernate version by their name.



11 нояб. 2020 г., в 11:19, Alexey Goncharuk  
написал(а):

Hello Mikhail,

I see that now only Ignite dependencies are marked as 'provided', however,
it makes sense to move all libraries being integrated to the 'provided'
scope (for example, the Apache Camel dependency for camel-ext and so on).
This is how it is currently done for the spring-autoconfigure, and I
believe we should be consistent here: either always freeze the integrations
versions, or always assume a user will provide them externally.

Thoughts?

вт, 10 нояб. 2020 г. в 14:14, Mikhail Petrov :


Igniters,

It seems that we came to decision on change of Ignite dependency scopes
to "provided". Don't we?

The corresponding ticket [1] is ready to final review. Saikat Maitra
have already reviewed and approved PR [2].

Could some committer take a final look?

[1] - https://issues.apache.org/jira/browse/IGNITE-13634
[2] - https://github.com/apache/ignite-extensions/pull/28

On 28.10.2020 20:24, Saikat Maitra wrote:

Hi

Alex,

Yes, we can start releasing the extensions modules. I would like to also
help in releasing a few extensions, it will also help me to be

familiarized

with the release process.

Mikhail and I have been having discussion about whether we should use
provided scope for dependencies or shall we use 2.9.0 for ignite.version
for the extensions modules?

Jira : https://issues.apache.org/jira/browse/IGNITE-13621
PR : https://github.com/apache/ignite-extensions/pull/28/files

Please let us know your thoughts.

Denis,

We have the following jira ticket for documentation work for ignite
extensions releases.

https://issues.apache.org/jira/browse/IGNITE-12951

Please let us know if the scope in the issue looks good.

Regards,
Saikat


On Wed, Oct 28, 2020 at 10:28 AM Denis Magda  wrote:


Alex,

Should we create a dedicated ticket for the documentation changes or

can we

reuse IGNITE-13634? As a bare minimum, we need to update maven

artifacts'

names and versions:



https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations



-
Denis


On Wed, Oct 28, 2020 at 5:10 AM Alexey Goncharuk <
alexey.goncha...@gmail.com>
wrote:


Igniters,

Since Ignite 2.9 has been released, I think we can now release the
extension modules related to streaming.

I noticed that unlike spring autoconfigure, the streamer extensions
dependencies do not have provided scope, so I created a ticket to fix

that

[1]. Anything else we should fix before releasing the extensions?

[1] https://issues.apache.org/jira/browse/IGNITE-13634

--AG

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

[Alexey Zinoviev]

Yes, Model Export/Import for ML will be finished, now it's ready, but under
testing on my side.

ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov :

> I suggest to include CDC feature to the 2.10 scope.
>
> > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> написал(а):
> >
> > Igniters,
> >
> >
> > Can you clarify the issue statuses according to the Apache Ignite
> > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
> > issues which are expected to be included in 2.10 with the unknown
> > status:
> >
> > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > Vinogradov, Ivan Daschinskiy)
> > Will all related issues be included in the 2.10?
> >
> > - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey
> Chugunov)
> > Are we on the last mile with this for 2.10?
> >
> > - Consistency-related improvements for atomic caches [3] (Alexey
> Scherbakov)
> > Do we have the JIRA issue? Will the issue be included in 2.10?
> >
> > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > The issue [4] is in progress state. Will it be finished prior to code
> freeze?
> >
> > - SQL runtime statistics (Konstantin Orlov)
> > Do we have an IEP for this or JIRA issue?
> >
> > - ML Model export/import [5] (Alexey Zinoviev)
> > - Will the issue be finished?
> >
> >
> > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > [2]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > [3]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > [7]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> >
> > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov  wrote:
> >>
> >> Folks,
> >>
> >> I've created the release page on the Confluence. Feel free to mail in
> >> case of any errors.
> >>
> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
> >>
> >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov  wrote:
> >>>
> >>> Igniters,
> >>>
> >>>
> >>> Let's finalize the discussion [1] about the next upcoming major Apache
> >>> Ignite 2.10  release. The major improvements related to the proposed
> >>> release:
> >>> - Improvements for partition clearing related parts
> >>> - Add tracing of SQL queries.
> >>> - CPP: Implement Cluster API
> >>> - .NET: Thin client: Transactions
> >>> - .NET: Thin Client: Continuous Query
> >>> - Java Thin client Kubernetes discovery
> >>>
> >>> etc.
> >>> Total: 166 RESOLVED issues [2].
> >>>
> >>>
> >>> Let's start the discussion about Time and Scope, and also I propose
> >>> myself as the release manager of the Apache Ignite 2.10. If you'd like
> >>> to lead this release, please, let us know, I see no problems to chose
> >>> a better candidate.
> >>>
> >>>
> >>> Proposed release timeline:
> >>>
> >>> Scope Freeze: December 10, 2020
> >>> Code Freeze: December 24, 2020
> >>> Voting Date: January 18, 2021
> >>> Release Date: January 25, 2021
> >>>
> >>>
> >>> Proposed release scope:
> >>> [2]
> >>>
> >>>
> >>> WDYT?
> >>>
> >>>
> >>> [1]
> http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> >>> [2]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20
>
>

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

[Nikolay Izhikov]

I suggest to include CDC feature to the 2.10 scope.

> 11 нояб. 2020 г., в 16:06, Maxim Muzafarov  написал(а):
> 
> Igniters,
> 
> 
> Can you clarify the issue statuses according to the Apache Ignite
> Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
> issues which are expected to be included in 2.10 with the unknown
> status:
> 
> - Distributed environment tests [2] (Nikolay Izhikov, Anton
> Vinogradov, Ivan Daschinskiy)
> Will all related issues be included in the 2.10?
> 
> - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey 
> Chugunov)
> Are we on the last mile with this for 2.10?
> 
> - Consistency-related improvements for atomic caches [3] (Alexey Scherbakov)
> Do we have the JIRA issue? Will the issue be included in 2.10?
> 
> - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> The issue [4] is in progress state. Will it be finished prior to code freeze?
> 
> - SQL runtime statistics (Konstantin Orlov)
> Do we have an IEP for this or JIRA issue?
> 
> - ML Model export/import [5] (Alexey Zinoviev)
> - Will the issue be finished?
> 
> 
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> [2] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> [3] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> [4] https://issues.apache.org/jira/browse/IGNITE-11704
> [5] https://issues.apache.org/jira/browse/IGNITE-6642
> [6] https://issues.apache.org/jira/browse/IGNITE-13143
> [7] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> 
> On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov  wrote:
>> 
>> Folks,
>> 
>> I've created the release page on the Confluence. Feel free to mail in
>> case of any errors.
>> 
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
>> 
>> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov  wrote:
>>> 
>>> Igniters,
>>> 
>>> 
>>> Let's finalize the discussion [1] about the next upcoming major Apache
>>> Ignite 2.10  release. The major improvements related to the proposed
>>> release:
>>> - Improvements for partition clearing related parts
>>> - Add tracing of SQL queries.
>>> - CPP: Implement Cluster API
>>> - .NET: Thin client: Transactions
>>> - .NET: Thin Client: Continuous Query
>>> - Java Thin client Kubernetes discovery
>>> 
>>> etc.
>>> Total: 166 RESOLVED issues [2].
>>> 
>>> 
>>> Let's start the discussion about Time and Scope, and also I propose
>>> myself as the release manager of the Apache Ignite 2.10. If you'd like
>>> to lead this release, please, let us know, I see no problems to chose
>>> a better candidate.
>>> 
>>> 
>>> Proposed release timeline:
>>> 
>>> Scope Freeze: December 10, 2020
>>> Code Freeze: December 24, 2020
>>> Voting Date: January 18, 2021
>>> Release Date: January 25, 2021
>>> 
>>> 
>>> Proposed release scope:
>>> [2]
>>> 
>>> 
>>> WDYT?
>>> 
>>> 
>>> [1] 
>>> http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
>>> [2] 
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

[Maxim Muzafarov]

Igniters,


Can you clarify the issue statuses according to the Apache Ignite
Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
issues which are expected to be included in 2.10 with the unknown
status:

- Distributed environment tests [2] (Nikolay Izhikov, Anton
Vinogradov, Ivan Daschinskiy)
Will all related issues be included in the 2.10?

- Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey Chugunov)
Are we on the last mile with this for 2.10?

- Consistency-related improvements for atomic caches [3] (Alexey Scherbakov)
Do we have the JIRA issue? Will the issue be included in 2.10?

- Tombstone objects during rebalancing [4] (Alexey Scherbakov)
The issue [4] is in progress state. Will it be finished prior to code freeze?

- SQL runtime statistics (Konstantin Orlov)
Do we have an IEP for this or JIRA issue?

- ML Model export/import [5] (Alexey Zinoviev)
- Will the issue be finished?


[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
[2] 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
[3] 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
[4] https://issues.apache.org/jira/browse/IGNITE-11704
[5] https://issues.apache.org/jira/browse/IGNITE-6642
[6] https://issues.apache.org/jira/browse/IGNITE-13143
[7] 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation

On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov  wrote:
>
> Folks,
>
> I've created the release page on the Confluence. Feel free to mail in
> case of any errors.
>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
>
> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov  wrote:
> >
> > Igniters,
> >
> >
> > Let's finalize the discussion [1] about the next upcoming major Apache
> > Ignite 2.10  release. The major improvements related to the proposed
> > release:
> > - Improvements for partition clearing related parts
> > - Add tracing of SQL queries.
> > - CPP: Implement Cluster API
> > - .NET: Thin client: Transactions
> > - .NET: Thin Client: Continuous Query
> > - Java Thin client Kubernetes discovery
> >
> > etc.
> > Total: 166 RESOLVED issues [2].
> >
> >
> > Let's start the discussion about Time and Scope, and also I propose
> > myself as the release manager of the Apache Ignite 2.10. If you'd like
> > to lead this release, please, let us know, I see no problems to chose
> > a better candidate.
> >
> >
> > Proposed release timeline:
> >
> > Scope Freeze: December 10, 2020
> > Code Freeze: December 24, 2020
> > Voting Date: January 18, 2021
> > Release Date: January 25, 2021
> >
> >
> > Proposed release scope:
> > [2]
> >
> >
> > WDYT?
> >
> >
> > [1] 
> > http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> > [2] 
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20

Re: Incorrect failure handler exceptions

[Ivan Daschinsky]

Ilya, thanks for your effort.

ср, 11 нояб. 2020 г. в 14:28, Ilya Kasnacheev :

> Hello!
>
> The fix is now merged.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 3 нояб. 2020 г. в 22:51, Ivan Daschinsky :
>
> > There is not a big problem to fix it.
> >
> > 1. Blocked thread is detected by another worker. Currently we take dump
> > before printing it to log with zero depth. This can be easily fixed.
> >
> > 2. We should propagate BlockedThreadExceptiob to failureCtx with original
> > stacktrace of blocked thread. StackFrames, obtained in previous step, can
> > be used to construct stacktrace of BlockedThreadException.
> >
> >
> > вт, 3 нояб. 2020 г., 19:15 Ilya Kasnacheev :
> >
> > > Hello!
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13665
> > >
> > > The notorious problem with failure handler's thread dump, which nobody
> > has
> > > bothered to investigate, until now.
> > > "IgnitionEx$IgniteNamedInstance$2.apply"
> > >
> > > If anybody knows how to fix it, please suggest.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> >
>


-- 
Sincerely yours, Ivan Daschinskiy

[jira] [Created] (IGNITE-13693) Add flags field with tombstone support, update schema size to 2 bytes

[Alexey Goncharuk (Jira)]

Alexey Goncharuk created IGNITE-13693:
-

 Summary: Add flags field with tombstone support, update schema 
size to 2 bytes
 Key: IGNITE-13693
 URL: https://issues.apache.org/jira/browse/IGNITE-13693
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Incorrect failure handler exceptions

[Ilya Kasnacheev]

Hello!

The fix is now merged.

Regards,
-- 
Ilya Kasnacheev


вт, 3 нояб. 2020 г. в 22:51, Ivan Daschinsky :

> There is not a big problem to fix it.
>
> 1. Blocked thread is detected by another worker. Currently we take dump
> before printing it to log with zero depth. This can be easily fixed.
>
> 2. We should propagate BlockedThreadExceptiob to failureCtx with original
> stacktrace of blocked thread. StackFrames, obtained in previous step, can
> be used to construct stacktrace of BlockedThreadException.
>
>
> вт, 3 нояб. 2020 г., 19:15 Ilya Kasnacheev :
>
> > Hello!
> >
> > https://issues.apache.org/jira/browse/IGNITE-13665
> >
> > The notorious problem with failure handler's thread dump, which nobody
> has
> > bothered to investigate, until now.
> > "IgnitionEx$IgniteNamedInstance$2.apply"
> >
> > If anybody knows how to fix it, please suggest.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
>

Re: [DISCUSS] Release Ignite streamer extensions

[Nikolay Izhikov]

+1 to make extensions as independent as possible.

Doubt if we can do it for each module.
We have, ignite-hibernate_4.2, ignite-hibernate_5.1 modules that attached to 
specific hibernate version by their name.


> 11 нояб. 2020 г., в 11:19, Alexey Goncharuk  
> написал(а):
> 
> Hello Mikhail,
> 
> I see that now only Ignite dependencies are marked as 'provided', however,
> it makes sense to move all libraries being integrated to the 'provided'
> scope (for example, the Apache Camel dependency for camel-ext and so on).
> This is how it is currently done for the spring-autoconfigure, and I
> believe we should be consistent here: either always freeze the integrations
> versions, or always assume a user will provide them externally.
> 
> Thoughts?
> 
> вт, 10 нояб. 2020 г. в 14:14, Mikhail Petrov :
> 
>> Igniters,
>> 
>> It seems that we came to decision on change of Ignite dependency scopes
>> to "provided". Don't we?
>> 
>> The corresponding ticket [1] is ready to final review. Saikat Maitra
>> have already reviewed and approved PR [2].
>> 
>> Could some committer take a final look?
>> 
>> [1] - https://issues.apache.org/jira/browse/IGNITE-13634
>> [2] - https://github.com/apache/ignite-extensions/pull/28
>> 
>> On 28.10.2020 20:24, Saikat Maitra wrote:
>>> Hi
>>> 
>>> Alex,
>>> 
>>> Yes, we can start releasing the extensions modules. I would like to also
>>> help in releasing a few extensions, it will also help me to be
>> familiarized
>>> with the release process.
>>> 
>>> Mikhail and I have been having discussion about whether we should use
>>> provided scope for dependencies or shall we use 2.9.0 for ignite.version
>>> for the extensions modules?
>>> 
>>> Jira : https://issues.apache.org/jira/browse/IGNITE-13621
>>> PR : https://github.com/apache/ignite-extensions/pull/28/files
>>> 
>>> Please let us know your thoughts.
>>> 
>>> Denis,
>>> 
>>> We have the following jira ticket for documentation work for ignite
>>> extensions releases.
>>> 
>>> https://issues.apache.org/jira/browse/IGNITE-12951
>>> 
>>> Please let us know if the scope in the issue looks good.
>>> 
>>> Regards,
>>> Saikat
>>> 
>>> 
>>> On Wed, Oct 28, 2020 at 10:28 AM Denis Magda  wrote:
>>> 
 Alex,
 
 Should we create a dedicated ticket for the documentation changes or
>> can we
 reuse IGNITE-13634? As a bare minimum, we need to update maven
>> artifacts'
 names and versions:
 
 
>> https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
 
 
 
 -
 Denis
 
 
 On Wed, Oct 28, 2020 at 5:10 AM Alexey Goncharuk <
 alexey.goncha...@gmail.com>
 wrote:
 
> Igniters,
> 
> Since Ignite 2.9 has been released, I think we can now release the
> extension modules related to streaming.
> 
> I noticed that unlike spring autoconfigure, the streamer extensions
> dependencies do not have provided scope, so I created a ticket to fix
 that
> [1]. Anything else we should fix before releasing the extensions?
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-13634
> 
> --AG
> 
>> 

Re: [DISCUSS] Release Ignite streamer extensions

[Alexey Goncharuk]

Hello Mikhail,

I see that now only Ignite dependencies are marked as 'provided', however,
it makes sense to move all libraries being integrated to the 'provided'
scope (for example, the Apache Camel dependency for camel-ext and so on).
This is how it is currently done for the spring-autoconfigure, and I
believe we should be consistent here: either always freeze the integrations
versions, or always assume a user will provide them externally.

Thoughts?

вт, 10 нояб. 2020 г. в 14:14, Mikhail Petrov :

> Igniters,
>
> It seems that we came to decision on change of Ignite dependency scopes
> to "provided". Don't we?
>
> The corresponding ticket [1] is ready to final review. Saikat Maitra
> have already reviewed and approved PR [2].
>
> Could some committer take a final look?
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-13634
> [2] - https://github.com/apache/ignite-extensions/pull/28
>
> On 28.10.2020 20:24, Saikat Maitra wrote:
> > Hi
> >
> > Alex,
> >
> > Yes, we can start releasing the extensions modules. I would like to also
> > help in releasing a few extensions, it will also help me to be
> familiarized
> > with the release process.
> >
> > Mikhail and I have been having discussion about whether we should use
> > provided scope for dependencies or shall we use 2.9.0 for ignite.version
> > for the extensions modules?
> >
> > Jira : https://issues.apache.org/jira/browse/IGNITE-13621
> > PR : https://github.com/apache/ignite-extensions/pull/28/files
> >
> > Please let us know your thoughts.
> >
> > Denis,
> >
> > We have the following jira ticket for documentation work for ignite
> > extensions releases.
> >
> > https://issues.apache.org/jira/browse/IGNITE-12951
> >
> > Please let us know if the scope in the issue looks good.
> >
> > Regards,
> > Saikat
> >
> >
> > On Wed, Oct 28, 2020 at 10:28 AM Denis Magda  wrote:
> >
> >> Alex,
> >>
> >> Should we create a dedicated ticket for the documentation changes or
> can we
> >> reuse IGNITE-13634? As a bare minimum, we need to update maven
> artifacts'
> >> names and versions:
> >>
> >>
> https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
> >>
> >>
> >>
> >> -
> >> Denis
> >>
> >>
> >> On Wed, Oct 28, 2020 at 5:10 AM Alexey Goncharuk <
> >> alexey.goncha...@gmail.com>
> >> wrote:
> >>
> >>> Igniters,
> >>>
> >>> Since Ignite 2.9 has been released, I think we can now release the
> >>> extension modules related to streaming.
> >>>
> >>> I noticed that unlike spring autoconfigure, the streamer extensions
> >>> dependencies do not have provided scope, so I created a ticket to fix
> >> that
> >>> [1]. Anything else we should fix before releasing the extensions?
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-13634
> >>>
> >>> --AG
> >>>
>